⬆️ Update GitHub Actions to latest versions

[frack113]

Summary

Update GitHub Actions to latest versions across all CI/CD workflows.

Changes

• ⬆️ Bumps:
  • Swatinem/rust-cache → v2.9.1
  • taiki/e/install-action → v2.82.1 (migrated to tool: syntax)
  • DavidAnson/markdownlint-cli2-action → v23.2.0
  • EmbarkStudios/cargo-deny-action → v2.0.20
• 🔧 Config: Replace yamllint max=120 with allow-non-breakable-words

[AntwortEinesLebens]

Honestly, I don't know how to think about this one. This is not a bad idea but the keeping it up to date is kind of a hell. Normally, we only need to secure the release pipeline. Using hash is almost the same as using the exact semver (v0.1.2 for example). It's also useful to use hash when a fix is here but yet release.

We should dive deeper for the pros and cons of this changes, I don't think it's a bad idea but we need more insight from other point of view for this one.

[frack113]

@AntwortEinesLebens thanks for the review. I addressed both of your points in recent commits:

1. dtolnay/rust-toolchain — changed back to pinning a commit hash (4be9e76fd7c4901c61fb841f559994984270fce7) instead of stable, so supply chain safety is preserved. See commit 7ff12a7.

2. .yamllint.yaml — added allow-non-breakable-words and allow-non-breakable-inline-mappings as you suggested, and removed the obsolete # yamllint disable-line exception in lint.yaml (commit c34eb9f). The rules are sensible for CI/CD files with long URLs, SHAs, and action references.

Could you take another look when you get a chance?

[AntwortEinesLebens]

One last change and this is ready to go

[frack113]

✅ Fixed: removed max: 120 and wrapped the two lines exceeding 80 chars (SPDX comment in lint.yaml and # stable comment in build.yaml). yamllint passes now.