fix(iam-github-oidc-provider): Add Github OIDC thumbprints sorting

[antongo-papaya]

Description

Add github oidc provider thumbprints list sorting

Motivation and Context

After the introduction of #403 we started facing terraform drift changes in our nightly workflow runs.
It tries to store the same thumbprints in a different order because distinct function preserves ordering:

Terraform will perform the following actions:

  # aws_iam_openid_connect_provider.this[0] will be updated in-place
  ~ resource "aws_iam_openid_connect_provider" "this" {
        id              = "arn:aws:iam::***:oidc-provider/token.actions.githubusercontent.com"
        tags            = {
            "managedBy"      = "terragrunt"
        }
      ~ thumbprint_list = [
          - "1c58a3a8518e8759bf075b76b750d4f2df264fcd",
          - "f879abce0008e4eb126e0097e46620f5aaae26ad",
            "6938fd4d98bab03faadb97b34396831e3780aea1",
          + "f879abce0008e4eb126e0097e46620f5aaae26ad",
          + "1c58a3a8518e8759bf075b76b750d4f2df264fcd",
        ]
        # (4 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Storing the list in a sorted way should prevent this behavior.

Breaking Changes

no

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[bryantbiggs]

I'm more inclined to revert back to the original since https://github.com/aws-actions/configure-aws-credentials#recent-updates

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[bryantbiggs]

with the recent changes to how IAM is handling verification, I think we can close this for now. Thank you tho!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.