Use profile when creating Signin service when using login_session

[alextwoods]

Fix #7196 - credentials loaded from a login_session profile resolved the Signin client's configuration, such as region and endpoint_url, from the default profile instead of the profile that requested the credentials.

Motivation and Context

See #7196 - the LoginProfileCredentialsProviderFactory was creating its Signin service client without specifying any profile based overrides.

Modifications

Plumb the context's profile file/profile name through Signin client creation.

Testing

New and existing unit tests

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.

License

• I confirm that this pull request can be released under the Apache 2 license

[alextwoods]

Note - Added no-api-surface-area-change label since new method is package private and annotated with @SdkTestInternalApi

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.