fix(deps): update dependency commander to v15

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
commander	14.0.3 → 15.0.0

---

Release Notes

tj/commander.js (commander)

v15.0.0

Compare Source

Commander 15 is ESM only. This is expected to be seamless for ESM consumers, but some CommonJS consumers may hit issues with tooling requiring configuration for ESM-only dependencies. See Migration Tips below.

The release of Commander 15 moves Commander 14 into maintenance. Commander 14 will get security updates for
12 months (to May 2027). For more info see Release Policy.

Added

• show excess command-arguments in error message ([#​2384])

Fixed

• Breaking: only lone --no-* option sets default option value to true, default not implicitly set when define both positive and negative option in either order ([#​2405])
• update example to use compatible character for MINGW64 ([#​2475])

Changed

• Breaking: migrated Commander implementation from CommonJS to ESM ([#​2464])
• Breaking: Commander 15 requires Node.js v22.12.0 or higher (for require(esm)).
• dev: switch tests from Jest to node:test test runner ([#​2463])

Deleted

• Breaking: removed deprecated export of commander/esm.mjs ([#​2464])

Migration Tips

Commander 15 is ESM only, but this does not mean you need to migrate to ESM to use it. Importing ESM from CommonJS is
supported by Node.js, and Bun, and Deno. Hopefully it Just Works for you! However, you may be using a different runtime or
some other part of your setup that may not yet natively support importing ESM from CommonJS, such as your testing framework
or bundler.

If you have problems using Commander 15 in your environment, one option is stay on Commander 14 for now. Commander 14 will
get security updates until May 2027 and things will hopefully improve for your setup in the meantime.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• 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 was generated by Mend Renovate. View the repository job log.

[doistbot]

This PR updates Commander to v15, which introduces a stricter Node.js requirement.

Few things worth tightening:

• Commander v15 requires Node >=22.12.0, but the engines.node field still claims support for Node 20, which will cause installation failures; either revert this update to stay on Commander v14 or update the engines field to drop Node 20 support.

_{Share Feedback • Review Logs}

[doistbot]

🟠 P1 Commander v15 requires node >=22.12.0, but this package's engines.node field still claims support for Node 20 (^20.19.0 || >=22.12.0). This will cause EBADENGINE warnings or installation failures for users running Node 20. If you wish to maintain Node 20 support, you should revert this update and remain on Commander v14 (which receives security updates until May 2027). If you intend to drop Node 20 support, update the engines field in this file to match.