App Flow - participation, visit, and form creation

[ashleybot]

Fixes #4

This PR provides functionality for a very basic participation, visit, and form initialization. It does not go very far past the foundational functionality, for example:

• It does not check for existing legacy ids #49
• It does not automatically auto-increment to the next visit number when creating a new visit #50
• It does not add any UI logic to only allow specific visit types (for example, if they already have had an IVP then they cannot have another)
• It does not validate. It does not handle form validation, or checks for cross-form validation, or overall visit validation.

Some overall code structure was modified in this PR as well:

• [x] Visit kinds where changed from string to enum. Anywhere there is still a string visit kind (aka. "IVP" etc) should be changed to the enum form

The basic features this PR provides are:

• [x] Create a new participation https://localhost:4811/Participations/Create
• [x] Create a new visit from a participant's details. Be sure to choose the correct visit type and increment the next number. (Create a new participation first then go to the details view https://localhost:4811/Participations/Details/1)
• [x] Create a new form from a visit's details (Create a new visit first then go to the visit details view https://localhost:4811/Visits/Details/1)
• [x] Creating a new form does not modify properties in other forms or the visit overall (only forms with display attributes can be created)
• [x] Editing a form only modifies properties in the form being edited and not properties in other forms or the visit overall (only forms with display attributes can be edited)
• [ ] Each visit type should display a different set of forms and should follow the NACC requirements for different visit types https://naccdata.org/data-collection/forms-documentation/uds-3

[ashleybot]

@smiththay Thanks!

• [x] I removed A5 from TFP
• [x] It doesn't look like B1 is in the TFP (it's also not in the screenshot), can you confirm?
• [x] C2T has one additional question for the C2 that I'll add a card for, it will required a change in the api as well. This will be the fix for TIP C2 as well.
• [x] The T1 shows for TIP and TFP (I can see it in the screenshot you included), can you confirm?

[smiththay]

@ashleybot All good! I glanced over T1 because it was at the top *facepalm