Sqlalchemy 2.0 changes for test_scheduler_job.py

[kunaljubce]

Issue description: #59402

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[Copilot]

Pull request overview

This PR migrates test_scheduler_job.py to SQLAlchemy 2.0 syntax by replacing legacy .query() API calls with the modern select() construct. The changes remove deprecated SQLAlchemy 1.4 compatibility code and align with SQLAlchemy 2.0 best practices.

Key changes:

• Replaced .query().filter() patterns with session.scalars(select().where()) for retrieving objects
• Replaced .query().filter().scalar() with session.scalar(select().where()) for scalar values
• Updated count operations from .query().count() to len(session.scalars(select()).all()) or session.scalar(select(func.count()))
• Removed imports and conditional logic for SQLALCHEMY_V_1_4 and SQLALCHEMY_V_2_0 version checks

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
airflow-core/tests/unit/jobs/test_scheduler_job.py	Migrated all SQLAlchemy query operations from legacy .query() API to 2.0-style select() constructs, removed version compatibility code, and added proper .unique() calls for joinedload queries
.pre-commit-config.yaml	Added test_scheduler_job.py to the list of files checked by pre-commit hooks

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[shahar1]

Could you please address issues raised by Copilot?

[kunaljubce]

Could you please address issues raised by Copilot?

yeah I will get to these over the weekend

[Prab-27]

Looks good to me, great work!

[potiuk]

Nice :) Thanks!

[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 bd8e0d3 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