Resolve SA warnings in migrations scripts

[Taragolis]

{
  "category": "sqlalchemy.exc.RemovedIn20Warning",
  "message": "The legacy calling style of select() is deprecated and will be removed in SQLAlchemy 2.0.  Please use the new calling style described at select(). (Background on SQLAlchemy 2.0 at: [https://sqlalche.me/e/b8d9)",](https://sqlalche.me/e/b8d9)%22,)
  "filename": "airflow/migrations/versions/0102_2_3_0_switch_xcom_table_to_use_run_id.py",
  "lineno": 95,
  "when": "runtest",
  "node_id": "tests/integration/providers/qdrant/hooks/test_qdrant.py::TestQdrant::test_connection"
}

{
  "category": "sqlalchemy.exc.SAWarning",
  "message": "implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery.",
  "filename": "airflow/migrations/versions/0093_2_2_0_taskinstance_keyed_to_dagrun.py",
  "lineno": 407,
  "when": "runtest",
  "node_id": "tests/auth/managers/test_base_auth_manager.py::TestBaseAuthManager::test_security_manager_return_default_security_manager"
}

{
  "category": "sqlalchemy.exc.SAWarning",
  "message": "implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery.",
  "filename": "airflow/migrations/versions/0104_2_3_0_migrate_rtif_to_use_run_id_and_map_index.py",
  "lineno": 105,
  "when": "runtest",
  "node_id": "tests/auth/managers/test_base_auth_manager.py::TestBaseAuthManager::test_security_manager_return_default_security_manager"
}

{
  "category": "sqlalchemy.exc.SAWarning",
  "message": "implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery.",
  "filename": "airflow/migrations/versions/0105_2_3_0_add_map_index_to_taskfail.py",
  "lineno": 101,
  "when": "runtest",
  "node_id": "tests/auth/managers/test_base_auth_manager.py::TestBaseAuthManager::test_security_manager_return_default_security_manager"
}

---

^ 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 newsfragments.