Regenerate uv.lock after allowing kubernetes 36.x in cncf.kubernetes

[choo121600]

why

Bumped the kubernetes/kubernetes_asyncio constraints in providers/cncf/kubernetes/pyproject.toml but did not regenerate uv.lock, leaving it out of sync with pyproject.toml.
This makes the uv.lock static check fail on virtually every open PR.

This regenerates uv.lock (and the provider_dependencies.json.sha256sum trailing newline) to match, unblocking CI.

related: #68041

---

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.

[kaxil]

Thanks @choo121600