chore(deps): update dependency eslint to v9

[renovate]

This PR contains the following updates:

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

---

Release Notes

eslint/eslint (eslint)

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

---

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 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: java-components/management-console/src/main/webui/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @redhat-cloud-services/eslint-config-redhat-cloud-services@2.0.4
npm error Found: eslint@9.3.0
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.24.5
npm error   node_modules/@babel/eslint-parser
npm error     @babel/eslint-parser@"^7.19.1" from @redhat-cloud-services/eslint-config-redhat-cloud-services@2.0.4
npm error     node_modules/@redhat-cloud-services/eslint-config-redhat-cloud-services
npm error       dev @redhat-cloud-services/eslint-config-redhat-cloud-services@"^2.0.3" from the root project
npm error   3 more (@eslint-community/eslint-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.9.0" from @redhat-cloud-services/eslint-config-redhat-cloud-services@2.0.4
npm error node_modules/@redhat-cloud-services/eslint-config-redhat-cloud-services
npm error   dev @redhat-cloud-services/eslint-config-redhat-cloud-services@"^2.0.3" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^8.9.0" from @redhat-cloud-services/eslint-config-redhat-cloud-services@2.0.4
npm error   node_modules/@redhat-cloud-services/eslint-config-redhat-cloud-services
npm error     dev @redhat-cloud-services/eslint-config-redhat-cloud-services@"^2.0.3" 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-27T06_25_58_576Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-27T06_25_58_576Z-debug-0.log

[openshift-ci]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a redhat-appstudio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.25%. Comparing base (134f203) to head (57e29ab).

Additional details and impacted files

@@              Coverage Diff              @@
##               main    #1690       +/-   ##
=============================================
+ Coverage     44.55%   56.25%   +11.69%     
=============================================
  Files           279       14      -265     
  Lines         11973     2896     -9077     
  Branches       1433        0     -1433     
=============================================
- Hits           5335     1629     -3706     
+ Misses         6002     1052     -4950     
+ Partials        636      215      -421     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rnc]

@stuartwdouglas While most of the dependencies updates to eslint 9 ok it appears redhat-cloud-services/eslint-config-redhat-cloud-services is more problematic. It has https://github.com/RedHatInsights/frontend-components/blob/master/packages/eslint-config/package.json#L21 which conflicts with the major version upgrade with a conflicting peer dependency ( https://github.com/npm/rfcs/blob/main/implemented/0031-handling-peer-conflicts.md ).

I think eslint-config-redhat-cloud-services dates from the creation of the console itself and whether we need it is another question? For that matter I don't think the eslint scripts are run/checked either?