Switch profiler-edit from minimist to commander

[mstange]

No description provided.

[codecov]

Codecov Report

❌ Patch coverage is 59.37500% with 13 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.78%. Comparing base (9faa037) to head (08c584a).
⚠️ Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node-tools/profiler-edit.ts	59.37%	13 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6065   +/-   ##
=======================================
  Coverage   83.77%   83.78%           
=======================================
  Files         329      329           
  Lines       34547    34544    -3     
  Branches     9667     9675    +8     
=======================================
- Hits        28943    28941    -2     
+ Misses       5175     5174    -1     
  Partials      429      429           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[canova]

Nice!

[canova]

Nit: I think due to exitOverride() above, now the errors are being printed twice, one by commander and the second time here.

For example I tested this:

$ node node-tools-dist/profiler-edit.js --asdfsdf
error: unknown option '--asdfsdf'
error: unknown option '--asdfsdf'

Could we maybe add an early return like this?

  if (err instanceof CommanderError) {
      // Commander already wrote its own output and chose the
      // appropriate exit code.
      process.exit(err.exitCode);
    }

[mstange]

Oh, good catch!