Update actions/stale action to v10

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/stale	action	major	v9 → v10

---

Release Notes

actions/stale (actions/stale)

v10

Compare Source

---

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: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[sentry]

Bug: The stale workflow enables delete-branch: true but lacks the necessary permissions: contents: write, which will cause branch deletion to fail under modern repository security settings.
_{Severity: MEDIUM}

Suggested Fix

Add a permissions: block to the job in .github/workflows/stale.yml to explicitly grant contents: write permission, ensuring the action can delete branches as intended.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/stale.yml#L10-L16

Potential issue: The `stale.yml` workflow uses `actions/stale@v10` with the
`delete-branch: true` option. This option requires `contents: write` permission, but the
workflow file does not define a `permissions:` block to grant it. If the repository's
default workflow permissions are set to be restrictive (read-only), the action will
silently fail to delete branches when closing stale pull requests. This will cause
unused branches to accumulate in the repository, even though the rest of the action
(like closing the PR) will succeed.

_{Did we get this right? 👍 / 👎 to inform future reviews.}