fix: coerce should play well with parser configuration

[shadowspawn]

Relates to #2307 and #2161. Yargs does the coerce separately after yargs-parser, and should both apply the coerce values to the aliases and camel-case variations, but also not add them back if the parser configuration said not to include them in the results.

Use the fact that yargs-parser has already decided what variations belong in the results, and update just the naming variations already present in the results.

Fixes #2307, fixes #2311

[shadowspawn]

I noticed a subtle problem that if strip-dashed is true then the argv does not contain the parsed option with the dashed name so coerce is ignored, although the option was present in the input arguments. May or may not attempt to fix that in this PR too... So many permutations!

• camel-case expansion
• strip-aliased
• strip-dashed

[shadowspawn]

In #1872 coerce handling got promoted out of yargs-parser to support async, so the current code is relatively new and has been iteratively improving to fully reimplement the original behaviours and coverage.

[shadowspawn]

Looking at the yargs-parser implementation, that code works with argv and aliases without checking configuration options. That makes me more confident that heading in the right direction in this PR.

[bcoe]

@shadowspawn thanks for the contribution 😄