Swagger of `Bitwarden Public API` is unable to login due to `version_header_missing`

### Steps To Reproduce

The [Swagger UI](https://bitwarden.com/help/api/) of the `Bitwarden Public API` does not work, there is no documentation of the mandatory "Bitwarden-Client-Version" header at all.

1. call https://bitwarden.com/help/api/
2. click Authorize
3. enter a valid client_id & client_secret
4. click Authorize
5. `Auth error
Error: response status is 400, error: version_header_missing, description: No client version header found, required to prevent encryption errors. Please confirm your client is supplying the header: "Bitwarden-Client-Version"`

### Expected Result

Should return a token.

### Actual Result

`Auth error
Error: response status is 400, error: version_header_missing, description: No client version header found, required to prevent encryption errors. Please confirm your client is supplying the header: "Bitwarden-Client-Version"`

### Screenshots or Videos

_No response_

### Additional Context

_No response_

### Operating System

Windows

### Operating System Version

_No response_

### Web Browser

Chrome

### Browser Version

_No response_

### Build Version

the current state of the cloud environment

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Start at the Swagger UI for the Bitwarden Public API and reproduce the Authorize flow with valid credentials. Inspect the OpenAPI authorization definition for the required Bitwarden-Client-Version header; done means the documented Swagger flow sends it and returns a token instead of version_header_missing.

Written by the indexing model from the issue text.