cdklocal bootstrap creates S3 bucket in wrong region

Nobody has claimed this yet.

When I run `cdklocal bootstrap` I get the following output:

bootstrapped
⏳ Bootstrapping environment aws://000000000000/us-gov-west-1...
Trusted accounts for deployment: (none)
Trusted accounts for lookup: (none)
Using default execution policy of 'arn:aws:iam::aws:policy/AdministratorAccess'. Pass '--cloudformation-execution-policies' to customize.
CDKToolkit: creating CloudFormation changeset...
✅ Environment aws://000000000000/us-gov-west-1 bootstrapped.

`us-gov-west-1` is the correct region, but when I go to the localstack site and view s3 buckets:

cdk-hnb659fds-assets-000000000000-us-east-1

the bucket that gets created has the wrong suffix. It also shows up no matter which region I choose.

I haven't been able to figure out how to get it to create the s3 bucket in the correct region no matter what configuration or environment variables I setup.

Start by reproducing `cdklocal bootstrap` for `us-gov-west-1` and compare the reported environment with the S3 bucket suffix shown in LocalStack. Trace how the `cdklocal` entry point selects the region and how the bootstrap bucket is created. Done means the bucket region suffix matches the selected region and behavior is consistent across regions.

Written by the indexing model from the issue text.