chore(deps): update dependency @stylistic/eslint-plugin to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@stylistic/eslint-plugin (source)	^2.10.1 || ^3.0.0 -> ^4.0.0

---

Release Notes

eslint-stylistic/eslint-stylistic (@​stylistic/eslint-plugin)

v4.1.0

Compare Source

Features

• add module.exports named export for require(esm) compatibility (#​700) (668c955)

Documentation

• update merged note (07b08f1)

Chores

• merge lines-around-comment (#​691) (f59605b)
• merge space-before-blocks (#​698) (6e8554d)
• merge space-infix-ops (#​697) (1a1b388)
• remove unnecessary ternary expression (#​695) (66a4b18)

v4.0.1

Compare Source

Bug Fixes

• indent-binary-ops: handle { for left token check (#​693) (7f2740e)

Chores

• merge block-spacing (#​690) (b239b71)

v4.0.0

Compare Source

Features

• semi-spacing: support handling typescript (#​687) (8b76c93)
• space-infix-ops: allow to ignore types in ts variant (#​684) (c83ce20)

Chores

• release-please-mark (b894a75)

v3.1.0

Compare Source

Features

• generic-spacing: remove spaces in type param instantiation (#​677) (2a29e28)

v3.0.1

Compare Source

Bug Fixes

• deps: unpin typescript-eslint deps (#​673) (9fb672d)

---

Configuration

📅 Schedule: 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.

[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: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^8.0.0 || ^9.0.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"8.20.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^6.6.0 || ^7.0.0 || ^8.0.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   5 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error dev @stylistic/eslint-plugin@"^4.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@">=9.0.0" from @stylistic/[email protected]
npm error   node_modules/@stylistic/eslint-plugin
npm error     dev @stylistic/eslint-plugin@"^4.0.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 /runner/cache/others/npm/_logs/2025-02-27T07_11_03_757Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-02-27T07_11_03_757Z-debug-0.log