fix: parse options ending with 3+ hyphens

[0x2b3bfa0]

Options ending with three or more hyphens were being parsed as positional arguments because the options without key name regular expression didn't have a ^ beginning anchor.

• Closes Option with three or more trailing hyphens parsed as positional argument #433
• Related to fix(populate--): -- should always be array #354

[bcoe]

@0x2b3bfa0 this fix looks good to me, but I believe you've created your PR against the branch yargs:main rather than main, mind switching the branch you've created your pull against?

[0x2b3bfa0]

@bcoe, yargs:main means “the branch main under the yargs user or organization” as opposed to 0x2b3bfa0:main, which means “the branch main under the 0x2b3bfa0 user's fork” 🤔

It looks like this pull request should be safe to merge (?)

[0x2b3bfa0]

Continuous integration checks are red. Is it my fault, or just a transient issue? 🤔

[bcoe]

@0x2b3bfa0 It's not immediately clear to me what the regression might be, it might not be related to your code changes -- unfortunately it might be a little while until I can fix up tests.

Apologies for the delay on review.

[0x2b3bfa0]

@bcoe, #442 fixes the tests

[bcoe]

@0x2b3bfa0 thank you for the patch 🥳 apologies for the slow turn around.

[0x2b3bfa0]

Thank you very much!