chore(deps): update dependency @actions/core to v1.11.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@actions/core (source)	1.10.1 → 1.11.1

---

Release Notes

actions/toolkit (@​actions/core)

v1.11.1

• Fix uses of crypto.randomUUID on Node 18 and earlier #​1842

v1.11.0

• Add platform info utilities #​1551
• Remove dependency on uuid package #​1824

---

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 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 was generated by Mend Renovate. View the repository job log.

[sentry]

Bug: The bundled dist/index.js file was not rebuilt after updating dependencies. The action will run old code with @actions/core@1.10.1 instead of the intended 1.11.1.
_{Severity: CRITICAL}

Suggested Fix

Run the build script (npm run build) to regenerate the bundled dist/index.js file using the updated dependencies and commit the resulting changes.

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: package.json#L22

Potential issue: The pull request updates the `@actions/core` dependency from `1.10.1`
to `1.11.1` in `package.json`, but the bundled action file, `dist/index.js`, was not
regenerated. Since the GitHub Action is configured to execute `dist/index.js` directly,
it will continue to run the old code based on `@actions/core@1.10.1`. This means the bug
fixes and dependency changes in the newer version, such as the fix for
`crypto.randomUUID()` on Node 16, will not be applied, and the action will continue to
use the external `uuid` package unnecessarily. The dependency upgrade is effectively
inert.

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