Set per-Python-version lower bounds for jpype1 in JDBC provider

[potiuk]

Summary

Follow-up to #65532. Sets the jpype1 lower bound per Python version to the earliest
release that ships prebuilt binary wheels for that interpreter:

Python	Lower bound
3.10	>=1.4.0
3.11	>=1.4.1
3.12	>=1.5.0
3.13	>=1.5.1
3.14	>=1.7.0

The !=1.7.0 exclusion on macOS arm64 is preserved for Python 3.10–3.13 (no arm64
wheels in that release). For Python 3.14, 1.7.0 is the only version with cp314 wheels,
so it's allowed on all platforms (macOS arm64 users will need to build from source until
1.7.1 restores those wheels).

related: #65532

---

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

• Yes — Claude Opus 4.6 (1M context)

Generated-by: Claude Opus 4.6 (1M context) following the guidelines

[github-actions]

Backport failed to create: v3-2-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-2-test

You can attempt to backport this manually by running:

cherry_picker 26e2e78 v3-2-test

This should apply the commit to the v3-2-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.

[jscheffl]

Cool!