chore: update refs and docs w.r.t. newest release

[seantronsen]

Description

• Switches minority hash refs to tagged refs.
• Updates tagged refs for local actions to current release version.
• Updates documentation examples to use the current release tag.

Checklist

• My code follows the style guidelines of this project
• I have added/updated comments where needed
• I have added tests that prove my fix is effective or my feature works
• I have run make test (or equivalent) locally and all tests pass
• I have updated the relevant documentation (CLI examples, man pages, README, other docs, etc.)
• DCO Sign-off: All commits are signed off (git commit -s) with my real name and email
• REUSE Compliance:
  • Each new/modified source file has SPDX copyright and license headers
  • Any non-commentable files include a <filename>.license sidecar
  • All referenced licenses are present in the LICENSES/ directory

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Dependency update
• Build system/CI

---

• I agree to follow the Code of Conduct.

[synackd]

Looks like this still uses tags instead of hashes. Was that a mistake? @seantronsen

[seantrons]

Looks like this still uses tags instead of hashes. Was that a mistake? @seantronsen

No that's intentional, @alexlovelltroy mentioned in a different chat:

"The renovate bot will gradually move everything to SHA-pinning."

So I left the remaining tag refs under the interpretation the bot will make the necessary changes. I likely have more workflow PRs coming tomorrow, so I could also just knock it out then.