Extended User schema

[ptbrowne]

Since there were database migrations to be ran, a new postgres database was created, so that the preview db is not disrupted, see #1538 (comment) for context.

Changes to the database are applied as soon as the server is started, see the start command where there is a db:migrate command
Changes are applied to the database that is linked to the project through environment variables
All vercel deployments (preview / production) are connected to the same database
I think a better model would be to create a new database and connect manually it through environment variables that are scoped to the particular branch you are working on
I've created the database, and did that right now, a new deployment would be necessary for the build on the branch to pick up the new environment varialbes
I am going to run manually the migration to delete the columns, from my local env, and then we should be good

When this PR is merged:

• Delete database on Vercel
• Delete related environment variables that are scoped to the branch

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
visualization-tool	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 29, 2024 8:29am

[ptbrowne]

I added this in the README @bprusinowski