fix: stale-issue-cleanup version update

[alikulka]

The action points to the latest release version tag instead of the SHA.

[jonathan343]

Same question I have for #4419

Is there a reason we changed from using a SHAs to tags?

Using SHAs
If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches.

Source: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-pre-written-building-blocks-in-your-workflow#using-shas

[kellertk]

While you are correct that humans don't change the SHAs, Dependabot can and does. The SHA that you have been using is pointing to the main branch of the action, and Dependabot has been cutting you PRs to update that SHA to the latest every time we make an update to main.

So far, you've been accepting these PRs, but we use semantically-versioned release tags to prevent inadvertent breakage on the main branch. This did cause both stale-issue-cleanup and closed-issue-message to break in this repository, because the tip of main was broken at one point but we had not cut a new release. For example:

• Bump aws-actions/stale-issue-cleanup from c452909aaa3fd1be240576cb41c6dd7bcb95cc10 to 119dcadf8036efef52409d94132c9441c346285c #4407
• Bump aws-actions/stale-issue-cleanup from 413d85a1603df4f0a8158f5f3c8204ab1691313e to c452909aaa3fd1be240576cb41c6dd7bcb95cc10 #4403
• Bump aws-actions/stale-issue-cleanup from 2017b87caa8e25014362d434a980d60fa758f3af to 413d85a1603df4f0a8158f5f3c8204ab1691313e #4371
• Bump aws-actions/closed-issue-message from 80edfc24bdf1283400eb04d20a8a605ae8bf7d48 to 37548691e7cc75ba58f85c9f873f9eee43590449 #4358
• Bump aws-actions/closed-issue-message from 8b6324312193476beecf11f8e8539d73a3553bf4 to 80edfc24bdf1283400eb04d20a8a605ae8bf7d48 #4214

I'm not aware of any additional testing you're doing to verify that these SHAs are OK to update. This sort of defeats the immutability that you seek. SHAs are immutable, but they're just getting updated anyway.

This week we made changes to our release cycle to automatically update the semantic tags whenever there's a new release possible, and more comprehensive tests to prevent merging broken code to main. This PR is to bring your repositories in line with all of the other AWS SDK team's instantiation of the actions.

[jonathan343]

Got it, thanks for the clarification @kellertk!

I'll approve this PR.

@alikulka can you update #4419 to only include changes for aws-actions/closed-issue-message since there is some overlap between the two PRs.