feature: adding smarter unit test execution

[cmgoffena13]

Description

During plan, run unit tests only for models in the plan change set (added, modified, restated).
No-change plans skip tests by default.
--all-tests runs the full suite (previous default).

Addresses #5965

Test Plan

• Plan with model changes runs only those models’ unit tests
• Plan with no changes skips unit tests
• --all-tests runs the full suite (including no-change plans)
• --skip-tests still skips; incompatible with --all-tests
• Docs cover plan-scoped default and --all-tests

Checklist

• I have run make style and fixed any issues
• I have added tests for my changes (if applicable)
• All existing tests pass (make fast-test)
• My commits are signed off (git commit -s) per the DCO

[mday-io]

Most of the other flags are verb_*. should this be --include_all_tests, or something similar?

[mday-io]

Nice idea! I do worry about the default behavior being only running impacted model's unit tests. An indirect model change could take place (i.e., things like a SQLGlot upgrade changing rendering/types, or an engine adapter change) and then tests would fail silently for a long time before it's caught.

Also, would be good to add a console output (x tests skipped) when only some tests were selected.

[cmgoffena13]

@mday-io -- yeah, now that I have time to think about it, I think it would make more sense to flip the logic I have and maybe add a flag for smarter unit test execution, thoughts? That way we wouldn't change default behavior and its opt-in. I like the Skipped X tests as well. Just need to think of what the flag would be called. Maybe --only-relevant-tests -- not sure

[mday-io]

yeah, I think that's the safest option for now.

and, what about --test-changed-only which auto-passes the list of changed models in. and then also add --test-model TEXT which the user can specify which to run (i.e., orders_*, to parallel --select-model)