Hardcoded schema name breaks migrations with restricted permissions

[lechinoix]

Bug report

Describe the bug

• I setup my medusa store in my production database in a separate schema and I gave it only permissions on its own schema, but when running migrations I had to remove one hardcoded "public" schema name to make it work

System information

Medusa version (including plugins): 1.3.22
Node.js version:
Database: Postgres
Operating system: MacOS
Browser (if relevant):

Steps to reproduce the behavior

1. Create a user with GRANT ALL ON SCHEMA medusa TO "medusa-user";
2. Use this user in DATABASE_URL
3. Run yarn medusa migrations run
4. It will fail

[lechinoix]

I think we just need to remove the schema here and here