[db] Pass preferred region for token management

[FredKSchott]

Changes

• Currently, we create a short-lived Studio token through the Studio API.
• This is creating a race condition where the token is created in the API's region (iad) but not yet propagated to the region closest to the user (sjc, ams, etc). This presents as a "TOKEN_UNUAUTHORIZED" error because the region closest to the user assume's it's a bad token.
• This PR fixes the issue by capturing the region code closest to the user, and then passing that to the Studio API. The Studio API then makes sure that the token created/renewed/deleted will be instantly up-to-date in that region before returning.

Testing

• Manually

Docs

• N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: 3d47c57

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[natemoo-re]

Can't speak to the Studio side of this code, but this all seems reasonable to me!

[matthewp]

Needs API change, so blocking for the moment.