Good new is that pylance likes it and copies over the
singature and everything.
Bad news is that mypy does not support this yet python/mypy#8645
Other minor bad news is that non_generative is not typed. I've tried using a protocol
like the one in the comment but the signature is not ported over by pylance, so it's
probably best to just live without it to have the correct signature.

notes from mike:  these three decorators are at the core of getting
the library to be typed, more good news is that pylance will
do all the things we like re: public_factory, see
microsoft/pyright#2758 (comment)
.

For @_generative, we will likely move to using pep 673 once mypy
supports it which may be soon.  but overall having the explicit
"return self" in the methods, while a little inconvenient, makes
the typing more straightforward and locally present in the files
rather than being decided at a distance.   having "return self"
present, or not, both have problems, so maybe we will be able
to change it again if things change as far as decorator support.
As it is, I feel like we are barely squeaking by with our decorators,
the typing is already pretty out there.

Change-Id: Ic77e13fc861def76a5925331df85c0aa48d77807
References: #6810

All but one metaclass used internally can now
be replaced using __init_subclass__().  Within this
patch we remove:

* events._EventMeta
* sql.visitors.TraversibleType
* sql.visitors.InternalTraversibleType
* testing.fixtures.FindFixture
* testing.fixtures.FindFixtureDeclarative
* langhelpers.EnsureKWArgType
* sql.functions._GenericMeta
* sql.type_api.VisitableCheckKWArg (was a mixture of TraversibleType
  and EnsureKWArgType)

The remaining internal class is MetaOptions used by the
sql.Options object which is in turn currently mostly for
ORM internal use, as this type implements class level overrides
for the ``+`` operator.

For declarative, removing DeclarativeMeta in place of
an `__init_subclass__()` class would not be fully feasible as
it would break backwards compatibility with applications that
refer to this class explicitly, but also DeclarativeMeta intercepts
class-level attribute set and delete operations which is a widely
used pattern.   An option for declarative base to use
`__init_subclass__()` should be provided but this is out of
scope for this particular change.

Change-Id: I8aa898c7ab59d887739037d34b1cbab36521ab78
References: #6810

introduces:

1. new mapped_column() helper
2. DeclarativeBase helper
3. declared_attr has been re-typed
4. rework of Mapped[] to return InstrumentedAtribute for
   class get, so works without Mapped itself having expression
   methods
5. ORM constructs now generic on [_T]

also includes some early typing work, most of which will
be in later commits:

1. URL and History become typing.NamedTuple
2. come up with type-checking friendly way of type
   checking cy extensions, where type checking will be applied
   to the py versions, just needed to come up with a succinct
   conditional pattern for the imports

References: #6810
References: #7535
References: #7562
Change-Id: Ie5d9a44631626c021d130ca4ce395aba623c71fb

This complements the type annotations of the `ARRAY` class, in preparation of #12384.

This pull request is:

- [ ] A documentation / typographical / small typing error fix
	- Good to go, no issue or tests are needed
- [ ] A short code fix
	- please include the issue number, and create an issue if none exists, which
	  must include a complete example of the issue.  one line code fixes without an
	  issue and demonstration will not be accepted.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.   one line code fixes without tests will not be accepted.
- [x] A new feature implementation
	- please include the issue number, and create an issue if none exists, which must
	  include a complete example of how the feature would look.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.

Related to #6810

Closes: #12386
Pull-request: #12386
Pull-request-sha: c9513ce

Change-Id: If9df4708c8e597eedc79ee3990792fa6c72f1afe
(cherry picked from commit 0bf7e02)

### Description

This complements the type annotations of the `ARRAY` class, in preparation of #12384.

### Checklist

This pull request is:

- [ ] A documentation / typographical / small typing error fix
	- Good to go, no issue or tests are needed
- [ ] A short code fix
	- please include the issue number, and create an issue if none exists, which
	  must include a complete example of the issue.  one line code fixes without an
	  issue and demonstration will not be accepted.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.   one line code fixes without tests will not be accepted.
- [x] A new feature implementation
	- please include the issue number, and create an issue if none exists, which must
	  include a complete example of how the feature would look.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.

Related to #6810

Closes: #12386
Pull-request: #12386
Pull-request-sha: c9513ce

Change-Id: If9df4708c8e597eedc79ee3990792fa6c72f1afe

Improved static typing for `postgresql.array()` by making the type parameter (the type of array's elements) inferred from the `clauses` and `type_` arguments while also ensuring they are consistent.

Also completed type annotations of `postgresql.ARRAY` following commit 0bf7e02 and added type annotations for functions `postgresql.Any()` and `postgresql.All()`.

Finally, fixed shadowing `typing.Any` by the `Any()` function through aliasing as `typing_Any`.

Related to #6810

Closes: #12384
Pull-request: #12384
Pull-request-sha: 78eea29

Change-Id: I5d35d15ec8ba4d58eeb9bf00abb710e2e585731f

Improved static typing for `postgresql.array()` by making the type parameter (the type of array's elements) inferred from the `clauses` and `type_` arguments while also ensuring they are consistent.

Also completed type annotations of `postgresql.ARRAY` following commit 0bf7e02 and added type annotations for functions `postgresql.Any()` and `postgresql.All()`.

Finally, fixed shadowing `typing.Any` by the `Any()` function through aliasing as `typing_Any`.

Related to #6810

Closes: #12384
Pull-request: #12384
Pull-request-sha: 78eea29

Change-Id: I5d35d15ec8ba4d58eeb9bf00abb710e2e585731f
(cherry picked from commit 75c8e11)

Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]`
instead as `Column[Sequence[Any]]` previously. This only works with the `type_`
argument to Column, but that's not new.

This follows from a suggestion at
sqlalchemy#12386 (comment).

Related to sqlalchemy#6810.

Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]`
instead as `Column[Sequence[Any]]` previously. This only works with the `type_`
argument to Column, but that's not new.

This follows from a suggestion at
sqlalchemy#12386 (comment).

Related to sqlalchemy#6810.

Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new.

This follows from a suggestion at
#12386 (comment).

Related to #6810.

Closes: #12443
Pull-request: #12443
Pull-request-sha: 2fff4e8

Change-Id: I87b828fd82d10fbf157141db3c31f0ec8149caad
(cherry picked from commit 500adfa)

Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new.

This follows from a suggestion at
#12386 (comment).

Related to #6810.

Closes: #12443
Pull-request: #12443
Pull-request-sha: 2fff4e8

Change-Id: I87b828fd82d10fbf157141db3c31f0ec8149caad

Related to sqlalchemy#6810.

Related to sqlalchemy#6810.

Overloading of `__init__()` is needed, probably for the same reason as
it is in ReturnTypeFromArgs.

Related to sqlalchemy#6810.

The return type of `array_agg()` is declared as a `Sequence[T]` where `T` is bound to the type of input argument.

This is implemented by making `array_agg()` inheriting from `ReturnTypeFromArgs` which provides appropriate overloads of `__init__()` to support this.

This usage of ReturnTypeFromArgs is a bit different from previous ones as the return type of the function is not exactly the same as that of its arguments, but a "collection" (a generic, namely a Sequence here) of the argument types.  Accordingly, we adjust the code of `tools/generate_sql_functions.py` to retrieve the "collection" type from 'fn_class' annotation and generate expected return type.

Also add a couple of hand-written typing tests for PostgreSQL.

Related to #6810

Closes: #12461
Pull-request: #12461
Pull-request-sha: ba27cbb

Change-Id: I3fd538cc7092a0492c26970f0b825bf70ddb66cd

The return type of `array_agg()` is declared as a `Sequence[T]` where `T` is bound to the type of input argument.

This is implemented by making `array_agg()` inheriting from `ReturnTypeFromArgs` which provides appropriate overloads of `__init__()` to support this.

This usage of ReturnTypeFromArgs is a bit different from previous ones as the return type of the function is not exactly the same as that of its arguments, but a "collection" (a generic, namely a Sequence here) of the argument types.  Accordingly, we adjust the code of `tools/generate_sql_functions.py` to retrieve the "collection" type from 'fn_class' annotation and generate expected return type.

Also add a couple of hand-written typing tests for PostgreSQL.

Related to #6810

Closes: #12461
Pull-request: #12461
Pull-request-sha: ba27cbb

Change-Id: I3fd538cc7092a0492c26970f0b825bf70ddb66cd
(cherry picked from commit 543acbd)

Overloading of `__init__()` is needed, probably for the same reason as
it is in ReturnTypeFromArgs.

Related to sqlalchemy#6810.

Related to #6810.

Closes: #12462
Pull-request: #12462
Pull-request-sha: 5a131cc

Change-Id: Ie4494d61f815edefef6a896499db4292fd94a22a

Related to #6810.

Closes: #12462
Pull-request: #12462
Pull-request-sha: 5a131cc

Change-Id: Ie4494d61f815edefef6a896499db4292fd94a22a
(cherry picked from commit 864f79d)

Overloading of `__init__()` is needed, probably for the same reason as
it is in ReturnTypeFromArgs.

Related to sqlalchemy#6810.

Overloading of `__init__()` is needed, probably for the same reason as
it is in ReturnTypeFromArgs.

Related to sqlalchemy#6810.

Overloading of `__init__()` is needed, probably for the same reason as it is in `ReturnTypeFromArgs`.

Related to #6810.

Closes: #12463
Pull-request: #12463
Pull-request-sha: 701d979

Change-Id: I7e1bb4d2c48dfb3461725c7079aaa72c66f1dc03

Overloading of `__init__()` is needed, probably for the same reason as it is in `ReturnTypeFromArgs`.

Related to #6810.

Closes: #12463
Pull-request: #12463
Pull-request-sha: 701d979

Change-Id: I7e1bb4d2c48dfb3461725c7079aaa72c66f1dc03
(cherry picked from commit 09c1d3c)

Tipyng of mysql dialect.

possible breaking changes:

- on `visit_sequence`, `visit_true` and `visit_false` I changed the param names to be the same tht in the super class.
- Removed  `tostring` on `array`. `tostring` is deprecated since Python 3.2 and removed in Python3.9 so i guess we can remove that option altogheter.
- create_connect_args on aiomysql, added an unused param _translate_args, only to have same signature as super class.
-  delete _check_unicode_returns method. on MySQLDialect_mysqldb. I think is not used after https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/1946, and is calling to a super that I think doesnt exist anymore.
- delete _set_isolation_level, is unused, and has a super that doesnt exists anymore:
sqlalchemy@af1b916
- Separate _bitmap in enumerated to _bitmap and _inversed_bitmap to have type safety
- Add inheritance from log.Identified to MySQLTableDefinitionParser, because has the decorathor @log.class_logger

Related to issue :
sqlalchemy#6810

Closes: sqlalchemy#12164
Pull-request: sqlalchemy#12164
Pull-request-sha: b877cca

Change-Id: I37bd98049ff1a64d58e9490b0e5e2ea764dd1f73