flag parser doesn't catch short flag with typos

[cristiand391]

Describe the bug
for a flag --target-org/-o, if I type -oasdf oclif doesn't throw Error (1): Nonexistent flag as expected, but instead parses it as:

flag: -o
value: asdf

To Reproduce

1. install Salesforce CLI
2. run sf project deploy start -oasdf dreamhouse (or any command with short flag+typo):

➜  dreamhouse-lwc git:(main) sf project deploy start -oasdf dreamhouse
Error (1): Parsing --target-org
        No authorization information found for asdf.
See more help with --help

long flag names aren't affected by this:

➜  dreamhouse-lwc git:(main) sf project deploy start --target-orgasdf dreamhouse
Error (1): Nonexistent flag: --target-orgasdf
See more help with --help

Expected behavior
shoud get the non-existent flag err if the short flag has a typo

sf version:
@salesforce/cli/2.15.8 darwin-x64 node-v18.17.0

Environment (please complete the following information):

• OS & version: macos ventura
• Shell/terminal & version: zsh/alacritty

[git2gus]

This issue has been linked to a new work item: W-14378968

[mdonnalley]

@cristiand391 This is actually working as designed and it's a fairly well known pattern for unix commands

I'm not sure there's anything we can do to know whether -oasdf is a typo when -o is expecting a value. Also changing it now would be a breaking change. The only thing we could really do is add support for custom flag parsing so that CLIs can change this behavior if they want. But I'm not sure that would be worth the effort.