ModelsMigrationsSync barks on custom alembic_version table

[Yuriy Taraday]

I use different name for alembic_version table.

In tests my db_sync command will use some custom config with different 'version_table' setting, but to get a difference between models and tables generated by migrations ModelsMigrationsSync.test_models_sync creates MigrationContext without opts argument so it uses the default 'alembic_version' and my table appears with 'remove_table' action.

It looks like test case should either have a hook to return all config that is used to interact with Alembic or at least to allow user to specify 'version_table' setting somehow.