chore(deps): update dependency rimraf to v5.0.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rimraf	5.0.6 -> 5.0.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

isaacs/rimraf (rimraf)

v5.0.7

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 1pm and before 6pm every weekend" in timezone Europe/Dublin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[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: pnpm-lock.yaml

Scope: all 19 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/dagda1/cuttingedge/apps/frontendsupport:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@gsap%2Fshockingly: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/dagda1/cuttingedge/apps/frontendsupport

@gsap/shockingly is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[changeset-bot]

⚠️ No Changeset found

Latest commit: de5ebde

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR