chore: bring ui into monorepo

[andrewrisse]

Integrates the "new UI (lfaiui) into the monorepo.

New naming convention is "leapfrogai-ui"

Includes Keycloak code that will not work until Supabase is deployed in our clusters.

We will leave leapfrog-demo deployed as is since it does not use Keycloak yet.

closes #344
closes #307

[netlify]

✅ Deploy Preview for leapfrogai-docs canceled.

Name	Link
🔨 Latest commit	a5cd1a4
🔍 Latest deploy log	https://app.netlify.com/sites/leapfrogai-docs/deploys/661d3d34c573e80008176ba2

[gerred]

doing some initial change requests since this is gonna be a chonky review

[gphorvath]

If Supabase is a resource we are sharing between the API DB and UI, do we need to move the Supabase directory up a level? Not totally sure how that works.
@andrewrisse

[andrewrisse]

If Supabase is a resource we are sharing between the API DB and UI, do we need to move the Supabase directory up a level? Not totally sure how that works. @andrewrisse

That directory is for running Supabase locally with the UI although it does contain some migrations the frontend needs when setting up Supabase. I wonder if these could be moved up to a parent directory.

@gerred I'm thinking consolating the supabase migrations and setup should be a separate issue once we have a sucessful deployment. I still need this in my section of the repo until that's in place

[gerred]

If Supabase is a resource we are sharing between the API DB and UI, do we need to move the Supabase directory up a level? Not totally sure how that works. @andrewrisse

That directory is for running Supabase locally with the UI although it does contain some migrations the frontend needs when setting up Supabase. I wonder if these could be moved up to a parent directory.

@gerred I'm thinking consolating the supabase migrations and setup should be a separate issue once we have a sucessful deployment. I still need this in my section of the repo until that's in place

Agreed on migrations later.

[gerred]

Read through all the Svelte parts, looks like a really good start. We should consider something a little more robust for migrations.