Clarify how user can replace API key with PAT

[mirnawong1]

Contributions

• I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

Per user feedback in slack, the existing user token page should clarify or go into detail how a user should replace the api key. Currently, some users think they have to replace their API key in dbt Cloud with their new PAT.

Instead, they should use the PAT anywhere they previously used an API key:

To use a PAT instead of an API key, you'll need to include it in the Authorization header of your API requests. The header should look like this: Authorization: Bearer <your-token>.
Please note that you do not need to replace your API key with a PAT in the dbt Cloud UI. The option to rotate API keys is separate and is used for rotating existing API keys, not for replacing them with PATs.

Also the the 'user api tokens' in the callout doesn't direct the user anywhere and needs updating to #user-api-tokens

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/docs/dbt-cloud-apis/user-tokens#account-scoped-personal-access-tokens

Additional information

No response