pyproject: Use SQLAlchemy v2 mypy plugin

[tony]

See also: https://docs.sqlalchemy.org/en/20/orm/extensions/mypy.html

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3a2aec7) 69.87% compared to head (a25306c) 69.87%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #323   +/-   ##
=======================================
  Coverage   69.87%   69.87%           
=======================================
  Files           9        9           
  Lines         654      654           
  Branches       88       88           
=======================================
  Hits          457      457           
  Misses        191      191           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tony]

Deprecated

SQLAlchemy 1.4 introduced the first SQLAlchemy-native ORM typing support using a combination of sqlalchemy2-stubs and the Mypy Plugin. In SQLAlchemy 2.0, the Mypy plugin remains available, and has been updated to work with SQLAlchemy 2.0’s typing system. However, it should now be considered deprecated, as applications now have a straightforward path to adopting the new typing support that does not use plugins or stubs.

See: https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html#whatsnew-20-orm-declarative-typing

Deprecated since version 2.0: The SQLAlchemy Mypy Plugin is DEPRECATED, and will be removed possibly as early as the SQLAlchemy 2.1 release. We would urge users to please migrate away from it ASAP.

This plugin cannot be maintained across constantly changing releases of mypy and its stability going forward CANNOT be guaranteed.

Modern SQLAlchemy now offers fully pep-484 compliant mapping syntaxes; see the linked section for migration details.

See also: https://docs.sqlalchemy.org/en/20/orm/extensions/mypy.html