Ability to add a co-applicant

[SLDonnelly]

As an Applicant or TSC Admin I want the ability to add co-applicant agencies So That other users can view and update information on the seedlot registration form

Acceptance Criteria

• [ ] Given that applicants can view and update registration forms in INC and PND status, When a co-applicant agency is added, Then co-applicants can view and edit the seedlot registration form.
• [ ] Original applicant is locked
• [ ] Added Co-applicant is updatable

Additional information Reuse the " add orchard id function" (if possible). Ownership function is another option as well Business rule: non-TSC admin users can only edit seedlot registration forms when in INC or PND status UX = TBD

Definition of Done

• [ ] Ready to Demo in Sprint Review
• [ ] Does what I have made have appropriate test coverage?
• [ ] Documentation and/or scientific documentation exists and can be found
• [ ] Peer Reviewed by 2 people on the team
• [ ] Manual testing of all PRs in Dev and Prod
• [ ] QA from design team
• [ ] Merged

[RMCampos]

Changes at a first glance

• Create a new column (co-applicant agency) in the Seedlot table
• Create a new column in the seedlot audit table.
• Update the draft form table; (no need to create a column, it's saved as a JSON)
• Update frontend forms, steps, states
• Update backend APIs (create seedlot, submit seedlot, retrieve seedlot payload)

Q&A

• Will the co-applicant agency have different location? Yes, it can be a completely different client number.
• Can the TSC Admin remove/delete the original (firstly entered) applicant agency? Not, at this point.
• Can TSC Admin remove/delete a co-applicant agency? Yes, any time.
• The co-applicant it's not locked.
• Do we need to update the design to fit new changes? Yes
• Will this change affect ETL? ETL can ignore entirely.

Q&A round 2 (with Matheus)

• Can users have different co-applicants in each form step? NO (this only applies to step 0)
• Do we need to handle a default co-applicant? NO