fix: Update GitHub Actions and pre-commit hook versions

[bryantbiggs]

Description

• Update GitHub Actions to their latest versions:
  • actions/checkout v5 -> v7
  • actions/setup-node v6 -> v7
  • actions/setup-python v5 -> v7 (module specific workflows only)
  • actions/stale v10 -> v11
  • dessant/lock-threads v5 -> v6
  • cycjimmy/semantic-release-action v5 -> v6.0.0
  • jaxxstorm/action-install-gh-release v2.1.0 -> v3.0.0
  • clowdhaus/terraform-min-max v2.1.0 -> v3.0.1
  • hashicorp/setup-terraform v3 -> v4 (module specific workflows only)
• Update the tool versions used by the pre-commit workflow:
  • terraform-docs v0.20.0 -> v0.24.0
  • tflint v0.59.1 -> v0.64.0
• Update the release workflow dependencies:
  • semantic-release 25.0.0 -> 25.0.8
  • @semantic-release/changelog 6.0.3 -> 7.0.0
  • @semantic-release/git 10.0.1 -> 11.0.1
  • conventional-changelog-conventionalcommits 9.1.0 -> 9.3.1
• Update pre-commit hook versions via pre-commit autoupdate and re-format with pre-commit run -a
• Roll the hardened disk cleanup step out to all modules. The apt-get removals are now
  best effort, so a transient package mirror failure no longer fails the job.

Note on conventional-changelog-conventionalcommits

This is intentionally held at the 9.x line rather than the latest 10.x. Version 10 replaced
its handlebars templates with render functions, which require conventional-changelog-writer
v9. semantic-release 25 still resolves conventional-changelog-writer v8, so the preset
loads without error but every release note and changelog entry renders empty. This is tracked
upstream in semantic-release/release-notes-generator#992 and the
reasoning is recorded as a comment in the release workflow so it does not get "fixed" back
to 10.x by a future update.

Motivation and Context

• Keeps our workflows on supported action versions
• Standardizes the common CI files across modules so these updates stay automatable

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