[fix](multi-catalog)fix compatibility issue for s3 endpoint when use incompatible client

[wsjz]

Proposed changes

there are some incompatible issues when use s3 endpoint but use oss,obs,cos location, fix them.
fix #22784

When s3 endpoint in catalog properties or load properties:
"s3.endpoint=cos.mycloud.com"
we can se its value is to access cos.

And then, when the query location is "s3://bucket/key" , we should use s3 client, and fit it with the s3 properties.
For another, when the query location is "cosn://bucket/key" , we should use cos client, and fit it with the cos properties.

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[xiaokang]

run buildall

[wsjz]

run buildall

[hello-stephen]

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.91 seconds
stream load tsv: 542 seconds loaded 74807831229 Bytes, about 131 MB/s
stream load json: 20 seconds loaded 2358488459 Bytes, about 112 MB/s
stream load orc: 65 seconds loaded 1101869774 Bytes, about 16 MB/s
stream load parquet: 31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select: 29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size: 17162015210 Bytes

[wsjz]

run fe ut

[xiaokang]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.

[dataroaring]

LGTM