Catch stale entries in the Java SDK dependency trust list

[FrankYang0529]

Why

• java-sdk/gradle/verification-metadata.xml is a trust list. Gradle's strict mode fails on a checksum mismatch and on an artifact with no entry, but not on an entry nothing resolves any more.
• Regeneration only appends, so every version bump leaves the superseded checksums behind.

How

• Add scripts/ci/prek/regenerate_java_sdk_verification_metadata.py. It clears the component list first, so superseded entries disappear instead of accumulating. Regenerate metadata based on -PgitRef=HEAD. It also puts back the ASF header Gradle strips. It retries three times because Maven Central and the Gradle Plugin Portal fail often enough to matter.
• Add a regenerate-java-sdk-verification-metadata prek hook.

Verification

• prek run regenerate-java-sdk-verification-metadata --all-files

---

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

• Yes - Claude Code

---

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

[uranusjr]

I feel we don’t need --check; generally our approach is to simply regenerate, and let prek’s file changed detection do the checking (prek fails when files are changed by the hook). There should be a way to work around the license header.

Otherwise I think this is on the right track.

[FrankYang0529]

@uranusjr Thanks for the suggestion. I changed to use prek hook.

[jason810496]

Thanks for the update.

[jason810496]

Thanks for the follow-up.

[github-actions]

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

You can attempt to backport this manually by running:

cherry_picker 3e47fc3 v3-3-test

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