Wr/twinning

[WillieRuemmele]

What does this PR do?

Adds --dev-debug flag with enhancements
You can now --dev-debug --debug-filter sf:config to limit DEBUG statements
✅ : the current promote-verify uses the correct command

Acceptance Criteria

run a command with --dev-debug to see the debug output, should be equivalent to setting DEBUG=* before running a command

Testing Notes

--dev-debug results in * debug statements
--dev-debug --debug-filter <filter> will filter the debug statements

Checklist

• This change has been approved by the CLI Review Board or approval isn't required. Anything that adds/changes/deletes commands, flags, output, or json output has to be reviewed.
• Does this follow the deprecation policy?

What issues does this PR fix or reference?

@W-12152987@

[mshanemc]

QA notes

./bin/run env list --dev-debug
✅ does all the debug output as expected
✅ ran with a few flags (--sort with a value, --help) after --dev-debug
✅ ran with a non-* debug value (sf:core) and saw only those logs

example from the comments
config get --dev-debug target-dev-hub --json
❌ command fails with NoConfigKeysFoundError (code is deleting the required argument after --dev-debug)
💡 what if this code ensured that, if present, --dev-debug is the last arg (or penultimate arg if followed by a non-flag value) ? I'm not sure there's a good way to tell an arg from a debug value

[mshanemc]

QA notes:

previous issue fixed. Tried all of
./bin/run config get --debug-filter sf:core target-dev-hub --dev-debug
./bin/run config get --debug-filter sf:core target-dev-hub
./bin/run config get --dev-debug --debug-filter sf:core target-dev-hub
./bin/run config get --dev-debug --debug-filter target-dev-hub

All passed/failed as expected.