Backport of actions: pin to the latest approved workflows into release/1.18.x

[hc-github-team-secure-vault-core]

Backport

This PR is auto-generated from #29321 to be assessed for backporting due to the inclusion of the label backport/1.18.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@ryancragun
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Description

The genesis of this PR is updating our cache action due to older actions being shut down0. While not mentioned in the changelog, the migration guide does call out versions <3.4.0 or <4.2.0 as too old.1

Since I was updating cache I went ahead and updated minor versions of all our actions.

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

---

Overview of commits

• b239a71

[hashicorp-cla-app]

All committers have signed the CLA.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[ryancragun]

    deleted by us:   .github/actions/run-apupgrade-tests/action.yml
    deleted by us:   .github/workflows/benchmark-prevent-performance-degradations.yml
    both modified:   .github/workflows/ci.yml

[github-actions]

Build Results:
All builds succeeded! ✅