feat: refactor options can be provided via the config file

[otaviomacedo]

Allow the user to pass options via the config file:

{
  "app": "node bin/main.js",
  "refactor": {
    "dryRun": true
  }
}

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 10 lines in your changes missing coverage. Please review.

Project coverage is 80.04%. Comparing base (286b063) to head (7d98f60).

Files with missing lines	Patch %	Lines
packages/aws-cdk/lib/cli/cli.ts	0.00%	10 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #714      +/-   ##
==========================================
+ Coverage   79.38%   80.04%   +0.65%     
==========================================
  Files          49       49              
  Lines        7209     7215       +6     
  Branches      809      817       +8     
==========================================
+ Hits         5723     5775      +52     
+ Misses       1467     1418      -49     
- Partials       19       22       +3     

Flag	Coverage Δ
suite.unit	80.04% <0.00%> (+0.65%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[rix0rrr]

I have two questions here:

• Can you give me an example of the use cases for this? I'm struggling to think why a user would choose to always run cdk refactor in dryrun mode.
• This seems like a one-off solution for refactoring. Should we not build it in such a way that it works for all commands?

[otaviomacedo]

I have two questions here:

* Can you give me an example of the use cases for this? I'm struggling to think why a user would choose to always run `cdk refactor` in dryrun mode.

* This seems like a one-off solution for refactoring. Should we not build it in such a way that it works for all commands?

Yeah, you're right. I'll just close it and revisit this feature if someone asks for it.