update to commander@9.0.0, remove negated cli param defaults

[pedroslopez]

Change description

Supersedes #2911

In the latest version of commander, the behavior of default values for boolean options has changed (see tj/commander.js#1652). This affects our use of negated options with a default value.

With a param no-exports with default: false...

Previously (8.3.0):

$ roo run
params.export = true 

$ roo run --no-exports
params.export = false

Now (9.0.0):

$ roo run
params.export = false 

$ roo run --no-exports
params.export = false

This meant that roo run by default was no longer exporting records after the commander upgrade. Removing the default value from these negated boolean options returns the expected behavior.

Checklists

Development

• Application changes have been tested appropriately

Impact

• Code follows company security practices and guidelines
• Security impact of change has been considered
• Performance impact of change has been considered
• Possible migration needs considered (model migrations, config migrations, etc.)

Please explain any security, performance, migration, or other impacts if relevant:

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached where applicable.
• Relevant tags have been added to the PR (bug, enhancement, internal, etc.)

[evantahler]

Good research figuring this out!