DEVORTEX-6305: Document jobUids filter on content-assignments account endpoint

[Jackalx]

Summary

• Adds the optional jobUids query parameter (array of strings, maxItems: 200) to GET /vendors-api/v2/accounts/{accountUid}/content-assignments in the OpenAPI spec.
• Corresponds to the vendors-service change in Smartling/vendors-service#731, which added this filter to fix an oversized-response failure (~7.5MB unfiltered payload) for large accounts.
• The agency (/vendors-api/v2/agencies/{agencyUid}/content-assignments) and Smartling LS content-assignments endpoints also gained the same filter in the linked PR, but neither is present in this public spec today — nothing to update there.

Test plan

• npm test (swagger-repo validate) — confirmed the same 16 pre-existing validation errors appear identically on master before this change (unrelated endpoints: accounts-api/v2/.../projects, files-api/v2/.../file/import, MTTranslateItemRequest); this change introduces zero new validation errors.
• npm run build — bundles successfully; verified jobUids appears correctly in the generated web_deploy/swagger.json for getContentAssignmentsByAccount.

Jira: https://smartling.atlassian.net/browse/DEVORTEX-6305

[maescomua]

Review summary — jobUids filter documentation

This accurately documents the account-endpoint jobUids param and the maxItems: 200 matches the server-side limit. One gap:

• The schema declares items: { type: string } with no pattern/maxLength, but the server enforces alphanumeric-only, ≤20 chars per item (400 otherwise). Consumers following only this spec have no way to predict that rejection. Worth adding pattern: "^[A-Za-z0-9]{1,20}$" (or maxLength: 20 at minimum) to match.

No action needed on the agency endpoint — confirmed it was never part of this public spec, consistent with this PR's own description, and DEVORTEX-6305 doesn't ask for it either.