fix(deps): update dependency @actions/cache to v4

[tradeshift-renovate]

This PR contains the following updates:

Package	Type	Update	Change
@actions/cache (source)	dependencies	major	3.2.4 -> 4.0.0

---

Release Notes

actions/toolkit (@​actions/cache)

v4.0.0

Important changes

The cache backend service has been rewritten from the ground up for improved performance and reliability. The @​actions/cache package now integrates with the new cache service (v2) APIs.

The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in this release are fully backward compatible.

All previous versions of this package will be deprecated. We recommend upgrading to version 4.0.0 as soon as possible before February 1st, 2025.

If you do not upgrade, all workflow runs using any of the deprecated @​actions/cache packages will fail.

Upgrading to the recommended version should not break or require any changes to your workflows beyond updating your package.json to version 4.0.0.

Read more about the change & access the migration guide: reference to the announcement.

Minor changes

• Update @actions/core to 1.11.0
• Update semver 6.3.1
• Add twirp-ts 2.5.0 to dependencies

v3.3.0

• Update @actions/core to 1.11.1
• Remove dependency on uuid package #​1824, #​1842

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[tradeshift-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json