Update dependency @actions/core to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@actions/core (source)	2.0.3 → 3.0.1

---

Release Notes

actions/toolkit (@​actions/core)

v3.0.1

• Bump undici from 6.23.0 to 6.24.1 #​2348

v3.0.0

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

[codacy-production]

Pull Request Overview

This pull request currently contains no changes to the repository, as the provided diff is empty. While the title indicates a major dependency update, the package configuration and source code remain unchanged. It is important to note that the transition to the next major version of this dependency involves a breaking change that makes the package ESM-only. This shift requires the project to either be converted to ESM or to use dynamic imports for this dependency. Codacy analysis indicates the project is currently 'up to standards', but this reflects the lack of new code rather than a successful implementation of the upgrade.

About this PR

• The intended dependency upgrade introduces a breaking change by becoming ESM-only. If the project currently uses CommonJS, the application will fail at runtime unless migration steps (such as converting to ESM or using dynamic imports) are implemented.
• The pull request does not contain any file changes. The expected updates to the dependency configuration and any necessary source code adjustments are missing.

Test suggestions

• Verify dependency version update in package.json
• Verify application functionality after ESM-only breaking change migration

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify dependency version update in package.json
2. Verify application functionality after ESM-only breaking change migration

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}