pkg/repository/config/aws.go: GetAWSBucketRegion: missing region hint

[kaovilai]

What steps did you take and what happened:

Clone of regression: aws-sdk-go-v2 bump removed region hint breaking GetBucketRegion #8022 which fixed aws-plugin only.
This issue scope is velero repo pkg/repository/config/aws.go: GetAWSBucketRegion

Without fixing, you will encounter following when creating FSB/Velero Built-In Data Mover backup

Errors:
  Velero:    name: /postgresql-1-9xl5g message: /Error backing up item error: /failed to wait BackupRepository, errored early: backup repository is not ready: error to get identifier for repo django-ts-dpa-1-kopia-qg56w: failed to detect the region via bucket: oadp98581bxgnc: operation error S3: HeadBucket, resolve auth scheme: resolve endpoint: endpoint rule error, Invalid region: region was not a valid DNS name. 

discovered via https://issues.redhat.com/browse/OADP-5029
What did you expect to happen:

The following information will help us better understand what's going on:

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

• kubectl logs deployment/velero -n velero
• velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
• velero backup logs <backupname>
• velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
• velero restore logs <restorename>

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Velero features (use velero client config get features):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"