br: fix getting region failure with other s3 compatible storage

[WangLe1321]

Signed-off-by: WangLe1321 wangle1321@163.com

What problem does this PR solve?

Issue Number: close #39648

Problem Summary:

full backup get 403 error with message "failed to get region of bucket xxx" when use other s3 compatible storage.

What is changed and how it works?

modify not to use path style addressing when use other s3 compatible storage to get region.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  1. execute full backup with alibaba OSS and backup is success.
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• fengou1
• joccau

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[WangLe1321]

/run-check-issue-triage-complete

[WangLe1321]

/check-issue-triage-complete

[WangLe1321]

/run check-issue-triage-complete

[WangLe1321]

/run-unit-test

[WangLe1321]

/run-check_dev

[joccau]

LGTM

[joccau]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 33688dc

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #39693.

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/sqllogic-test-2	🟥 failed 1, success 27, total 28	6 min 41 sec	New failing
idc-jenkins-ci/integration-cdc-test	✅ all 40 tests passed	20 min	Fixed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	41 min	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 11 tests passed	11 min	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	7 min 23 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	6 min 23 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	6 min 11 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	4 min 2 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 4 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed