Run tests on chart 1-2x line

[Miretpl]

Somewhere during Helm Refurbish works and separation of Chart 2.0 (main) and 1.2x (chart/v1-2x-test) release lines, we missed that the CI is not running on the chart branch. As I think that after 1.22 release we will probably have one more e.g. due two missing deprecation warnings, I thought that it would be good to have CI running for 1-2x line. This PR adds matching for new chart-related branches and:

1. disables all provider-related test cases
2. disables all ui e2e-related test cases

Some test cases are disabled as tracking and fixing them by backporting from main is rather too time consuming, having in mind that they are not strictly connected to the chart itself, and also the fact that 1-2x line will not live long.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[jscheffl]

Thanks for the initiative adding CI on chart branch!

I am not sure actually about how it is best. General changes like checks against main or similar like in https://github.com/apache/airflow/pull/66832/changes#diff-c6f469502ccc758f597b999e8ab5aebeba2ae82fb6dc8166e7d8a25969bcf3faR1475 might be better changed in main as well and then cherry-picked on the maintenance. Upgrade of UV is okay but usually we should separate the PRs... whereas this might be OK.

@potiuk WDYT is the easiest, best and long term strategy for the additional maintenance branches? Probably this PR is okay but not sure if you have other thoughts or a more general change in test selection for the maintenance branches? Similar might come soon for task SDK and Airflow CTL? So maintenance branches will grow.

[potiuk]

@potiuk WDYT is the easiest, best and long term strategy for the additional maintenance branches? Probably this PR is okay but not sure if you have other thoughts or a more general change in test selection for the maintenance branches? Similar might come soon for task SDK and Airflow CTL? So maintenance branches will grow.

This is pretty expected, yes. So I am fine with this change.