Autogenerate does not consider schema for enum type

Describe the bug
I am using Postgres 12, Alembic (1.7.1) and SQLAlchemy (1.4.23)
and have something like this SQLAlchemy enum in my model:

class MyEnum(enum.Enum):
    one= 'one'
    two= 'two'

...

my_enum = Column(Enum(MyEnum), nullable=False)

When I run
alembic revision --autogenerate

I get in my migration script:

sa.Column('my_enum',
          sa.Enum('one', 'two', name='myenum'),
          nullable=False),

I am using another schema than the default (public) one and while there is a schema arg that can be set (and I am currently changing the script manually adding it), it is not being considered by autogenerate. For stuff like tables and so on, it works perfectly and the schema is considered.

Expected behavior
I'd like to see the following being autogenerated for my example case:

sa.Column('my_enum',
          sa.Enum('one', 'two', name='myenum', schema='my_schema_name'), 
          nullable=False),

Versions.

• OS: Ubuntu 20.04
• Python: 3.8.10
• Alembic: 1.7.1
• SQLAlchemy: 1.4.23
• Database: Postgres 12
• DBAPI:

Start by reproducing the issue with alembic revision --autogenerate using a non-public schema and inspect the generated migration script for the SQLAlchemy Enum column. Trace how autogenerate handles the Enum schema argument, then verify that the generated sa.Enum includes the model's schema without manual edits.