feat: First Time Setup Wizard

[michael-genson]

What type of PR is this?

(REQUIRED)

• feature

What this PR does / why we need it:

(REQUIRED)

This PR adds a first time setup wizard. It was first proposed in #1164, but getting this ready before V1 would've been too much. Now that we're past V1, we're in a good place to add this sort of thing.

When a user logs-in as the default user ([email protected]), or they go to the root URL while logged-in with the default user (index), they are redirected to /admin/setup. Here they perform a few tasks:

1. Change their email, username, and password
2. Toggle public access
3. Toggle seed data

Once that's complete, they're given a list of places to check out (e.g. migrations).

Here's a full walkthrough of the new setup wizard:

I think there's more that can be done here to help new setups, but as-is I'm pretty happy with how it turned out, and adding-on to it should be pretty straight-forward.

Which issue(s) this PR fixes:

(REQUIRED)

N/A, idea comes from #1164

Fixes 2166

Special notes for your reviewer:

(fill-in or delete this section)

A few implementation notes:

• In order to avoid having the user re-type their password (since they're going to be using the default password anyway) I added a sort of workaround to the update password route on the backend. If the user trying to update their password is the default user, and they don't provide the current password, we assume they meant to provide the default password. I added test cases for this
• If the site is in demo mode, the setup page is skipped (as if you're not logging-in as the default user, even if you are)
• I refactored the new user registration form so I didn't have to duplicate it here. Hopefully I didn't make too much of a mess of things, but that was probably the hardest part of this PR, so take a look if you can. I did end-to-end testing to confirm registration still works as expected. I don't know if I used the form composable correctly, so definitely give that an extra look over

Testing

(fill-in or delete this section)

Added a backend test for the update password change, and did end to end testing for new instances as well as registrations (since that draws from the same code)

[hay-kot]

Pulled down and tested, everything looks good to me besides my one comment about verifying the current password.

[michael-genson]

It's lost in the merge commit but I removed the backend password stuff (I just let the OIDC PR overwrite the changes since there was a conflict there anyway)