Update GitHub Action actions/create-github-app-token to v3.2.0

[hash-worker]

This PR contains the following updates:

Package	Type	Update	Change
actions/create-github-app-token	action	minor	v3.0.0 → v3.2.0

---

Release Notes

actions/create-github-app-token (actions/create-github-app-token)

v3.2.0

Compare Source

Features

• add support for enterprise-level GitHub Apps (#​263) (952a2a7)
• support full repository names in repositories input (#​372) (85eb8dd)

Bug Fixes

• deps: bump @​actions/core from 3.0.0 to 3.0.1 in the production-dependencies group (#​364) (43e5c34)
• validate private-key input (#​376) (f24bbd8)

v3.1.1

Compare Source

Bug Fixes

• improve error message when app identifier is empty (#​362) (07e2b76), closes #​249

v3.1.0

Compare Source

Bug Fixes

• deps: bump p-retry from 7.1.1 to 8.0.0 (#​357) (3bbe07d)

Features

• add client-id input and deprecate app-id (#​353) (e6bd4e6)
• update permission inputs (#​358) (076e948)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 2am on saturday"
• Automerge
  • "before 4am every weekday,every weekend"

🚦 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.

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the pinned commit for actions/create-github-app-token in the housekeeping dependencies workflow.

Why: Moves from v3.0.0 to v3.1.1 to pick up upstream fixes/features.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[cursor]

PR Summary

Low Risk
Single pinned action upgrade in CI with unchanged secrets and inputs; no application or auth logic changes.

Overview
Pins actions/create-github-app-token in the centralized Renovate workflow (housekeeping-dependencies.yml) from v3.0.0 to v3.2.0 (commit SHA updated). The Get token step still uses Vault-provided app-id and private-key; only the action version changes.

Upstream v3.1–v3.2 adds optional inputs (e.g. client-id), stricter private-key validation, and enterprise-app / repository-name handling—none of which alter how this workflow is configured today.

^{Reviewed by Cursor Bugbot for commit 3c76120. Bugbot is set up for automated code reviews on this repo. Configure here.}