more options for config file generation

[phlptp]

Add a way to control whether only active subcommand defaults are written to a config file.

[phlptp]

Fixes #541

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (e4ee3af) to head (a7bbf03).
⚠️ Report is 188 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##              main     #1314     +/-   ##
===========================================
  Coverage   100.00%   100.00%             
===========================================
  Files           17        19      +2     
  Lines         4546      5139    +593     
  Branches         0      1100   +1100     
===========================================
+ Hits          4546      5139    +593     

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

[phlptp]

@henryiii I either need to be given permissions to modify the configuration on codacy for CLI11 or you need to disable the missing include check or I am going to disable all the codacy check. Right now it is not useful given the number of false positives it is generating.

[henryiii]

I disabled the pattern on one of them, I think/hope that will disable all of them on the next run. AFAICT you should have access already, if you sign in with GitHub; I think it just uses the GitHub permissions?

[phlptp]

I can see everything but I can't change the settings for the projects as best as I can tell. On my other projects I have access to a code_patterns tab and settings tab in Codacy where I can change that but on cli11 I can just see issues. Hopefully that change propagates and it is a non-issue going forward.

[phlptp]

I will merge tomorrow morning unless there are objections or comments.