Do not strip excess leading dashes on long option names

[shadowspawn]

Problem

All leading dashes on options are being stripped. This was to allow -foo treated the same as --foo for some circumstances, but that approach is being reconsidered to fully support short option flags and have simple consistent behaviour.

Note: the preflight checks in current limited code mean this is only affecting two or more dashes.

See #7 and #2

Solution

Only strip the two leading dashes of an option with two or more leading dashes.

---foo is parsed as an option named -foo.

(I followed the lint rules for the test file, rather than the local code style. I did not modify the rest of the file to pass the linter to keep this PR focused.)

[bcoe]

@joesepi personally, I think this is a good resolution to #7, if you provide an extra dash you get the variable -foo, this is nice because the person using the library can then choose how they deal with this value.

[bcoe]

I think the tests will need to be updated to flags.

[shadowspawn]

Test updated.

[bcoe]

Asking for forgiveness rather than permission, as this was open for a couple weeks 😆

I like this simplfication to the parser.