Add Support for STS regional Endpoints

[masum13]

What feature do you want to see added?

When adding an AWS Credential to Jenkins that includes a Role ARN, the plugin will only use the commercial STS endpoint (sts.amazonaws.com) to retrieve temporary credentials. This means you cannot specify a Role ARN if you are supplying credentials in a private network where an internet connection is not available.
The feature should dynamically select the appropriate STS Endpoint based region example,
If we try to connect the sts endpoint from the eu-west-1 region and the global endpoint isn't able to connect due to an internet connection it should try to connect region-based endpoint [ sts.eu-west-1.amazonaws.com ].

Upstream changes

No response

[AntonioDLuffy]

Just wanted to echo that this issue is still very relevant. The AssumeRole operation continues to use the global STS endpoint (sts.amazonaws.com). This is problematic for latency and compliance reasons, and I did not find a reliable way to enforce the use of regional STS endpoints with the existing plugin setup.

Could you confirm if this issue will be resolved as part of the effort to remove AWS SDK v1 in issue #284?