Modify breeze cache test to use constant for supported Python versions

[Dev-iL]

Fix a Breeze cache test that hard-coded the supported Python versions list.

check_if_values_allowed() returns the canonical list from Breeze global constants, but dev/breeze/tests/test_cache.py still expected only 3.10 through 3.13. Once Python 3.14 was added, the test started failing even though the implementation was correct.

This change updates the test to use ALLOWED_PYTHON_MAJOR_MINOR_VERSIONS, so it stays aligned with the supported versions defined by Breeze and does not need a manual update on every new Python minor release.

related: #63520

---

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

• Yes (please specify the tool below)

Generated-by: Codex GPT-5.4 following the guidelines

---

• 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.

[jason810496]

Good catch!

[github-actions]

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 6a1c3b5 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.