Hello there, I've got a question around the automatic table updates done by the supertokens-postgresql image. Is it possible to disable them so the container will connect to the database and assume that everything is already set up properly? The reason I'm asking is because I'm adding a self hosted container and have created all the tables/indices that the container needs as part of a schema in the db already. I've given the container a separate user with all privileges on the schema as well as all the tables within it to limit access to the other schemas within the db. The problem is is that when the container connects, it starts running commands like:

CREATE INDEX IF NOT EXISTS passwordless_codes_device_id_hash_index ON supertokens.passwordless_codes(app_id, tenant_id, device_id_hash)

Despite the index existing already. It doesn't have access to do this as it doesn't own the table. So the container startup fails unfortunately. Thanks for your time.