165 feature user registration after azure login

[kaiyangzheng]

Description

• Make department names unique, and position names in a department unique
• Change seed back to my email
• Create new register route in auth service to register new employees
• Update department and position service to search by name
• Update authConfig to query for more values from ms api
• Call register endpoint in frontend
• Restore smooth navigation by memoing wrapper
• Add transition animation to form image card

Motivation and Context

• We want users to be able to login even if their account is not present in the database

Closes [#152]

How has this been tested?

Logging in user and making sure appropriate database rows are created.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
mfa-form-automator	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 21, 2024 11:40pm

[laurenbrissette]

I feel like it might be better to have finding in a separate function that both findOneByName and findOrCreateOneByName use, just so the logic is only in one place.

[ahweigl]

This is easily doable but I think for the sake of keeping the service logic explicit/clear the same query can exist in both functions, it's only a few lines + there's a subtle difference in making the department variable mutable ie let department = in findOrCreateOneByName so that it can be overwritten

[ahweigl]

LGTM