400 Bad Request for any command

**Expected Behavior**

I expect to be able to see my orgs, programs, etc. I also expect to be able to access (read/write) configuration for them.

**Actual Behavior**

Any command returns Error: 400 (Bad Request)

**Reproduction Scenario, Platform, and Version**

npm --version
8.1.3

aio -v
@adobe/aio-cli/8.2.0 darwin-x64 node-v14.16.0

aio plugins
@adobe/aio-cli-plugin-cloudmanager 2.26.1

If this is related to authentication, include the output of `aio config:get ims.contexts.aio-cli-plugin-cloudmanager` but *do not* include the private key content *or* any access tokens.

Output of aio config:get ims.contexts.aio-cli-plugin-cloudmanager is nothing, not even a blank line.

**Steps to Reproduce**

Steps to reproduce the behavior:
1. `npm install -g @adobe/aio-cli`
2. `aio plugins:install @adobe/aio-cli-plugin-cloudmanager`
3. `aio plugins:update`
4. `aio auth:login` Followed by the program opening a browser, logging in, and seeing the Adobe I/O success message.
5. `aio cloudmanager:org:list` <- returns Error: 400 (Bad Request)
6. `aio cloudmanager:org:select` <- returns Error: 400 (Bad Request)

No source file or test is named. Start by reproducing the failure with aio auth:login, aio cloudmanager:org:list, and aio cloudmanager:org:select, then inspect the authentication context and request handling that produces the 400 response. Done means the commands can access and select organizations without returning 400.

Written by the indexing model from the issue text.