chore(deps): replace dependency eslint-plugin-node with eslint-plugin-n ^14.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
eslint-plugin-node	devDependencies	replacement	^11.1.0 -> ^14.0.0

This is a special PR that replaces eslint-plugin-node with the community suggested minimal stable replacement version.

---

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 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 unable to resolve dependency tree
npm error
npm error While resolving: ibm-watson@9.0.1
npm error Found: eslint@6.8.0
npm error node_modules/eslint
npm error   dev eslint@"^6.8.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=7.0.0" from eslint-plugin-n@14.0.0
npm error node_modules/eslint-plugin-n
npm error   dev eslint-plugin-n@"^14.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 /tmp/renovate/cache/others/npm/_logs/2024-04-26T23_50_45_352Z-eresolve-report.txt

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: ibm-watson@10.0.0
npm error Found: eslint@6.8.0
npm error node_modules/eslint
npm error   dev eslint@"^6.8.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=7.0.0" from eslint-plugin-n@14.0.0
npm error node_modules/eslint-plugin-n
npm error   dev eslint-plugin-n@"^14.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-04-26T23_58_11_470Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-26T23_58_11_470Z-debug-0.log