Sync uv.lock and provider-deps checksum for #66612

[FrankYang0529]

#66612 added SQL auto-lineage support to the Informatica provider and declared two new dependencies in
providers/informatica/pyproject.toml — sqlglot>=30.0.0 and the common-sql extra (apache-airflow-providers-common-sql). It updated generated/provider_dependencies.json, but the matching uv.lock and
generated/provider_dependencies.json.sha256sum were not regenerated, leaving the repository in an inconsistent state.

The task generate-tasksdk-datamodels in pre-commit-config runs uv run -p 3.12 --no-progress --active --group codegen --project apache-airflow-task-sdk --directory task-sdk -s dev/generate_task_sdk_models.py and updates uv.lock file.

related: #66612

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.

[eladkal]

Fix error in Generate Datamodels for TaskSDK client.

related: #66612

Can you be more specific? traceback? reproduce steps?
The related issue does not clarify what is the problem you are trying to solve

[FrankYang0529]

Can you be more specific? traceback? reproduce steps?
The related issue does not clarify what is the problem you are trying to solve

Sorry for that. I updated PR description for more background. I will avoid to give unclear context next time. I tried to fix OpenLineage issue for s3 (#68619) and cannot push commit successfully cause of uv.lock and generated/provider_dependencies.json.sha256sum. Use another PR for this because it's not related to the change in #68619.

[Lee-W]

I also encountered the same issue during development. and just verified it's still there