[CT-1947] Alias --models to --select for all commands except dbt ls

[aranke]

resolves #6782

Description

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[aranke]

Crazy to think that a few line changes have allowed nearly 100(!) additional tests to pass.

Before: 134 failed, 444 passed
After: 43 failed, 535 passed

[ChenyuLInx]

LGTM.

[ChenyuLInx]

Nit: this is simpler code but slightly harder to read compared to just write the options here.

[MichelleArk]

Did some manual testing by locally overwriting a command that accepts the new select (--select, --model) alias command with print(ctx.obj["flags"].SELECT) and found some issues when passing --select and --model to a command together.

The options are not treated as mutually exclusive via MultiOption and the resulting flags.SELECT value is clobbered by the value from the last alias option:

❯ python3 core/dbt/cli/main.py docs generate --select model_a model_b  --model model_c
('model_c',)

❯ python3 core/dbt/cli/main.py docs generate --model model_c --select model_a model_b
('model_a', 'model_b')

This was unexpected behaviour to me, but for better or for worse this is also how main's parsing currently works (printing args.select and exiting on main to test):

❯ dbt docs generate --select model_a model_b --model model_c
['model_c']
❯ dbt docs generate --select model_a model_b --model model_c
['model_c']
❯ dbt docs generate --model model_c --select model_a model_b 
['model_a', 'model_b']

We should probably open an issue to document this behaviour and investigate a fix that gets us --select/--model option mutual exclusivity if possible. But given that it's the current behaviour on main I don't see it as pressing to fix as part of this PR.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.