feat: Support usage of AWS Profiles

[jfeddern]

Issue #, if available: #1586 and #112

Description of changes:

This feature adds support for named AWS profiles to the configure-aws-credentials GitHub Action, enabling users to configure multiple AWS profiles in a single workflow and write credentials to standard AWS configuration files (~/.aws/credentials and ~/.aws/config) instead of only exporting them as environment variables.

Motivation

Previously, the action only supported exporting credentials as environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN), which created several limitations:

1. No multi-profile support: Impossible to configure multiple AWS accounts/roles in a single workflow job
2. Tool compatibility issues: Many tools (Terraform, AWS CDK, multi-account scripts) expect credentials in ~/.aws/credentials and ~/.aws/config files
3. Profile switching: No way to easily switch between different AWS contexts in a single job
4. Standard AWS CLI workflows: Users couldn't use aws --profile commands

Solution

Add an optional aws-profile input that, when provided, writes credentials to AWS configuration files in standard INI format, allowing natural integration with AWS CLI, SDKs, and infrastructure-as-code tools.

---

• Have you followed the guidelines in our Contributing guide?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.