Update dependency eslint to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	^8.10 -> ^9.0.0

---

Release Notes

eslint/eslint (eslint)

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 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. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error   peer eslint@">= 8" from @croct/[email protected]
npm error   node_modules/@croct/eslint-plugin
npm error     dev @croct/eslint-plugin@"^0.7.0" from the root project
npm error   6 more (@eslint-community/eslint-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"^7.0.0" from the root project
npm error   peer @typescript-eslint/parser@">= 6" from @croct/[email protected]
npm error   node_modules/@croct/eslint-plugin
npm error     dev @croct/eslint-plugin@"^0.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/parser
npm error     dev @typescript-eslint/parser@"^7.0.0" from the root project
npm error     peer @typescript-eslint/parser@">= 6" from @croct/[email protected]
npm error     node_modules/@croct/eslint-plugin
npm error       dev @croct/eslint-plugin@"^0.7.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-01T00_40_48_432Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-01T00_40_48_432Z-debug-0.log

[github-actions]

👋 @renovate[bot]

Thanks for your contribution!

The approval and merge process is almost fully automated 🧙

Here's how it works:

1. You open a new pull request
2. Automated tests check the code
3. Maintainers review the code
4. Once approved, the PR is ready to merge.

👉 Omit the extended description
Please remove the commit body before merging the pull request.
Instead, include the pull request number in the title to provide the full context
about the change.

☝️ Lastly, the title for the commit will come from the pull request title. So please provide a descriptive title that summarizes the changes in 50 characters or less using the imperative mood.

Happy coding! 🎉