Multi-schema postgis extension error on deploying to new database

[marcellmueller]

Describe the bug
This is a pretty critical issue we need to solve. For some reason our deployment works differently in RDS than it does locally or using docker-compose. I thought it was solved however it's cropped up again when I renamed our database, as well as recently when Om was testing the new s3 import.

We are unsure if it's Flyway or something RDS related.

What we know about this:

• We deploy our RST schema and install postgis;
• We deploy our FST schema, it says postgis exists so it doesn't install
• We get an error saying that type geometry doesn't exist for flyway schema

How I 'fixed' it for deployment is going into the query editor, doing drop extension 'postgis' cascade; then create extension 'postgis' cascade and then redeploying the flyway task. However I believe this is a bandaid fix, I suspect that the RST schema will error with geometry does not exist once we start adding geometry fields to that schema.

edit:
Found this while reading the docs for something unrelated, we may need to create a role to manage the extension
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Appendix.PostgreSQL.CommonDBATasks.PostGIS.html