Make using DB-specific indexes (FULLTEXT) raise warning rather then error under sqlite

Is your feature request related to a problem? Please describe.
Sqlite is kind of convenient to use for testing, but i have features specific to my DB, e.g FULLTEXT-index. I don't really need to test them, but their presence makes sqlite unusable since tortoise throws a bunch of operational errors.

Describe the solution you'd like
Something like warnings would be fine. Or helpful error when using DB-specific features. Just something for this to work with limitations.

Describe alternatives you've considered
The only alternative for sqlite right now is patching, but it is quite hard without breaking something.
I can use specific DB (mysql in my case), but i think there should be solution when i use only common DB features.

Additional context
Maybe this feature should somehow be enabled for testing purposes only. At the end, you really should not use DB-specific features if you plan to allow usage of different databases.

No files or tests are named in the issue. Start by tracing how Tortoise handles database-specific indexes when using SQLite, then compare the MySQL behavior; done means FULLTEXT or similar indexes no longer make SQLite unusable and the limitation is surfaced as a warning or helpful error.