Which problem is this pull request solving?

In #158, we've added experimental support for configurable regions to deploy-scoped stores (i.e. stores created with getDeployStore()). It works as follows:

• For API calls (i.e. when using an API token), you can use getDeployStore({ experimentalRegion: "auto" }) to instruct the API to choose the same region as the one configured for functions
  • If this parameter is not supplied, the Blobs client will not send any region parameter to the API, which means the default region will be used
• For edge calls (i.e. when using a token from a serverless function or an edge function), you can use getDeployStore({ experimentalRegion: "context" }) to instruct the CDN to choose the region defined in the environment
  • If a region is not defined in the environment, an error will be thrown
  • This should not happen, since we're populating the environment with a region in all contexts (serverless functions, edge functions, and the CLI)

This PR introduces the following changes:

• The experimentalRegion parameter is removed
• A new region parameter is added to the getDeployStore method, which takes the name of a region
• For API calls, a region is now always sent to the API
  • If a region has been specified via the region parameter, that will be used
  • If not, the client will use auto
• For edge calls, a region is now always sent to the CDN
  • If a region has been specified via the region parameter, that will be used
  • If not, the region specified in the context will be used, if one is set
  • If not, an error will be thrown

Technically, this is a breaking change because getDeployStore() now selects the functions region by default instead of the default region, accessing the same store using different versions of the Blobs client might generate different reasons, since they may be pointing to different regions.

Should you want to update your Blobs client but keep accessing a deploy-scoped store that has been created with an older version, you can use getDeployStore({ region: "us-east-2" }) to ensure you're using the right region.