fix: Prevent Users From Being Created With Missing Group/Household

[michael-genson]

What type of PR is this?

(REQUIRED)

• bug

What this PR does / why we need it:

(REQUIRED)

Currently there are a couple of ways of creating users with invalid groups/households. This puts the app into a broken state where it won't run (because Pydantic complains about the missing group/household). This PR catches this issue at the db level so at least users/developers are aware of why (and when) this happens.

Now upon user creation, if the group or household is invalid a ValueError is raised:

# Invalid Group
Group "GROUPNAME" does not exist; cannot create user

# Invalid Household on a valid Group
Household "HOUSEHOLDNAME" does not exist on group "GROUPNAME" (GROUPID); cannot create user

Which issue(s) this PR fixes:

(REQUIRED)

Fixes #4480

Special notes for your reviewer:

(fill-in or delete this section)

@cmintey as far as I know this mostly only impacts LDAP/OIDC user creation. If possible/reasonable it's probably worth addressing this in a more user-friendly way (unsure if it's possible to configure a group/household using the user's auth service?) but at least this will prevent bad things from happening. It also gives the user a reasonable log to work with.

Testing

(fill-in or delete this section)

Added tests to LDAP and OpenID which trigger this issue. Users are no longer created in a bad state.

[cmintey]

LGTM. The ability to assign users to a group and household upon creation (and re-assign households upon login) is on my todo list. Just haven't had time to fully flesh out the details on it