Spike: basing it all on supabase

[mike-hogan]

The idea of supporting N backend types is nice, but If we doubled down on supabase, that might increase velocity and focus.

Auth, storage, database, graphql, permissions, rest etc

And it's a good bet for the long run.

Spike it out

• [x] fire up supabase free
• [ ] migrate the schema into existence
• [ ] test the graphql api
• [ ] wire in the data editor to issue mutations back to supabase

[mike-hogan]

• [ ] rework backend/api/src/routes/models.ts to work with one supabase postgres
• [ ] credentials can be in environment variables for now, ie no need to store secrets yet
• [ ] check the graphql api in supbase works
• [ ] test we can make a model in model editor, and apply it to supabase, and see it in supabase console etc

[mike-hogan]

Not basing it on supabase gql any more. That requires a schema per tenant which is not the supabase model. So we're going to try multi-tenanted model and record storage based on json, with a multi-tenanted gql api dynamically generated from that