Refactor tests for shared distributions

[potiuk]

• Dynamically detect shared distributions in selective checks
• Run the tests as matrix
• Skip cleaning the worker and setting up docker and breeze
• Install the version of uv that we are bound with
• Run tests in parallel wiht xdist

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[amoghrajesh]

One qn: if changes are made in shared/timezones, will it run tests only for that or for all shared?

[potiuk]

One qn: if changes are made in shared/timezones, will it run tests only for that or for all shared?

All tests. They are fast in case of those shared utils. I prefer to run them always for everything (similarly as we run always all prek hook for --all-files in CI

[potiuk]

All tests. They are fast in case of those shared utils. I prefer to run them always for everything (similarly as we run always all prek hook for --all-files in CI

• 40 s for test (including env setup) ... Not worth to risk selective checks for those (at least not for now).

[gopidesupavan]

Nice :)

[gopidesupavan]

All tests. They are fast in case of those shared utils. I prefer to run them always for everything (similarly as we run always all prek hook for --all-files in CI

• 40 s for test (including env setup) ... Not worth to risk selective checks for those (at least not for now).

make sense as these components are very critical running always good choice :).

[amoghrajesh]

One qn: if changes are made in shared/timezones, will it run tests only for that or for all shared?

All tests. They are fast in case of those shared utils. I prefer to run them always for everything (similarly as we run always all prek hook for --all-files in CI

Yep, I was expecting that too. The shared components also could inter depend on each other, so it would make sense too

[potiuk]

Random k8s tests

[amoghrajesh]

Nice thanks @potiuk!