Update files in prevent deprecated sqlalchemy prek hook

[Prab-27]

Related : here
and here

closes : #59402 and #45461

---

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 or {issue_number}.significant.rst, in airflow-core/newsfragments.

[Prab-27]

I only included modules that have python files , Do I need to chnage any module that are not using SQLAlchemy - sessions ?

[Prab-27]

Thanks @shahar1 for approval !

Some Tests are failing .... Looking into it !

[shahar1]

Thanks @shahar1 for approval !

Some Tests are failing .... Looking into it !

Anytime :)
Not sure if it's related to these changes though, probably related to the existing ci/cd issues reported on the Slack channel.

[Prab-27]

@shahar1 , Yes !! That's true

[shahar1]

@shahar1 , Yes !! That's true

I think it should have been fixed.
Rebased, hopefully it will pass this time.

[Prab-27]

All green !!!

[github-actions]

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

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker bc22a99 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.