Fix intermittent credential problem on Windows

[sobolk]

Problem

We're getting intermittent InvalidSignatureException exception in our e2e tests. This seems to happen:

1. On Windows only.
2. With e2e-tooling profile only.
3. First SDK call with e2e-tooling profile seems to be failing, regardless of scenario.

This has been triaged to match: https://github.com/aws-actions/configure-aws-credentials/issues/599 and https://github.com/aws-actions/configure-aws-credentials/issues/528

Example

Changes

Use special-characters-workaround which was added to handle this particular case.

Docs: https://github.com/aws-actions/configure-aws-credentials/blob/97834a484a5ab3c40fa9e2eb40fcf8041105a573/action.yml#L73-L75

Validation

This PR run.

Checklist

• [ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• [ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• [ ] If this PR requires a docs update, I have linked to that docs PR above.
• [ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: bb3d26e0d6228d527691cfbc5672deb92d06cc3f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR