br: fix backup to aliyum OSS not support ak/sk as env (#54150)

[ti-chi-bot]

This is an automated cherry-pick of #54150

What problem does this PR solve?

Issue Number: close #45551

Problem Summary:

What changed and how does it work?

Fix the problem that BR only accept credentials from ISM service.
Now, if the BR can't get the ISM credentials, it will try to retrieve credentials from other sources.
And even if it got, it will still try to apply env provider and then shared provider first.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Protocol:

1. Set access-key and secret-access-key as my local machine environmental variable.
2. Try br backup full from a public address (my local machine) without ISM access-key.
3. Check if the full backup task finished and if the Aliyun OSS server received the backup files.

Result:

1. On my local machine:

./bin/br backup full     --pd "localhost:45129"     --storage "s3://test-cred/backup-data-2?endpoint=https://oss-cn-beijing.aliyuncs.com&provider=alibaba" --check-requirements=false
Detail BR log in /tmp/br.log.2024-06-27T15.12.35+0800 
Full Backup <------------------------------------------------------------------> 100.00%
Checksum <---------------------------------------------------------------------> 100.00%
[2024/06/27 15:13:10.064 +08:00] [INFO] [collector.go:77] ["Full Backup success summary"
] [total-ranges=13] [ranges-succeed=13] [ranges-failed=0] [backup-checksum=75.981913ms] [backup-fast-checksum=59.160314ms] [backup-total-ranges=119] [backup-total-regions=119] [total-take=34.226278783s] [BackupTS=450749369217187841] [total-kv=1402] [total-kv-size=409kB] [average-speed=11.95kB/s] [backup-data-size(after-compressed)=92.64kB] [Size=92636]                                                                                      

2. On the Aliyun OSS machine

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.

Fix the problem that BR only accept credentials from ISM service.
Now, if the BR can't get the ISM credentials, it will behave as same as other endpoints and try to retrieve credentials from other sources. 
And even if it got, it will still try to apply env provider and then shared provider first.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 15 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@42b624c). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #54994   +/-   ##
================================================
  Coverage               ?   72.5558%           
================================================
  Files                  ?       1466           
  Lines                  ?     435707           
  Branches               ?          0           
================================================
  Hits                   ?     316131           
  Misses                 ?      99111           
  Partials               ?      20465           

Flag	Coverage Δ
unit	72.5558% <0.0000%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	57.8032% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	41.0576% <0.0000%> (?)

[BornChanger]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, BornChanger

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

The pull request process is described here

Needs approval from an approver in each of these files:

• br/pkg/storage/OWNERS [3pointer,BornChanger]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-31 09:20:53.331859772 +0000 UTC m=+347569.611907855: ☑️ agreed by BornChanger.
• 2024-08-05 04:04:51.079384929 +0000 UTC m=+238420.946484002: ☑️ agreed by 3pointer.

[RidRisR]

/retest

[YuJuncen]

/retest-required

[BornChanger]

/retest

[BornChanger]

/retest

[BornChanger]

/retest