Update dependency @actions/github to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@actions/github (source)	8.0.1 → 9.1.1

---

Release Notes

actions/toolkit (@​actions/github)

v9.1.1

• Bump undici from 6.23.0 to 6.24.0 #​2346

v9.1.0

• Append actions_orchestration_id to user-agent when the ACTIONS_ORCHESTRATION_ID environment variable is set #​2364

v9.0.0

• Breaking change: Package is now ESM-only
  • CommonJS consumers must use dynamic import() instead of require()
  • Example: const { getOctokit, context } = await import('@​actions/github')
• Fix TypeScript compilation by migrating to ESM, enabling proper imports from @octokit/core/types

---

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

The update to the dependency introduces a breaking change by transitioning to an ESM-only format. However, the current submission does not contain any code or configuration changes to address this transition or the dependency update itself. This gap prevents the PR from meeting its stated acceptance criteria and poses a high risk of runtime failures due to module system incompatibilities.

About this PR

• The package transition to ESM-only requires verified architectural adjustments. Without visible changes to handling imports or project configuration, the application is unlikely to initialize correctly.
• The PR contains no file changes. To satisfy the intent of updating the dependency, the manifest files and any necessary configuration adjustments for ESM compatibility must be included.

Test suggestions

• Verify that the application/action can successfully import and initialize the dependency despite its ESM-only nature.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the application/action can successfully import and initialize the dependency despite its ESM-only nature.

_{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.}