Update dependency @actions/core to v3

[renovate]

This PR contains the following updates:

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

---

Release Notes

actions/toolkit (@​actions/core)

v3.0.0

• Breaking change: Package is now ESM-only
  • CommonJS consumers must use dynamic import() instead of require()

v2.0.3

• Bump @actions/http-client to 3.0.2

v2.0.1

• Bump @​actions/exec from 1.1.1 to 2.0.0 #​2199

v2.0.0

• Add support for Node 24 #​2110
• Bump @​actions/http-client from 2.0.1 to 3.0.0

---

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: A deep import from @actions/core/lib/summary.js will fail at runtime because v3.0.0 of the package is ESM-only and does not export this internal path.
_{Severity: CRITICAL}

Suggested Fix

Update the import statement to use the main package entry point, which is a supported public API. Change the import from import type { SummaryTableRow } from '@actions/core/lib/summary.js'; to import type { SummaryTableRow } from '@actions/core';.

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/actions/package.json#L14

Potential issue: The code imports a type using a deep path: `import type {
SummaryTableRow } from '@actions/core/lib/summary.js';`. While this compiles
successfully due to the `"moduleResolution": "bundler"` setting, it will cause a runtime
failure. The build configuration marks `@actions/core` as an external package, so the
import is resolved by Node.js when the action runs. The updated v3.0.0 of
`@actions/core` is ESM-only and does not expose this internal path in its `package.json`
exports map. This will result in an `ERR_PACKAGE_PATH_NOT_EXPORTED` error, causing the
GitHub Action to crash on startup.

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