GraphQL Query: Send Application

[ronaldheft-gov]

• Creates a new applicationSend mutation to support sending the application to UAP (Resolves #308).
  • This calls the stored procedure SP_SEND_APPLICATION.
  • SP_SEND_APPLICATION expects a DISCLAIMER_UNDERSTOOD value, which has been added as a GraphQL ENUM ApplicationDisclaimerUnderstood.
  • This mutation returns a new APPLICATION_NUMBER that the front-end must reference going forward. The previous APPLICATION_NUMBER that matches the USER_ID is no longer valid after submission.
• Creates a new applicationConfirmation query to return the confirmation details of the submitted application (Resolves #309).
  • This query requires the APPLICATION_NUMBER from applicationSend.
  • There is security in place to ensure a user can only access their submitted application (so they can't lookup other users' applications). <- This could use some extra validation to ensure I implemented it correctly.
• This PR does not handle sending the confirmation email to the user.
  • Upon further investigation, I discovered the current confirmation sent is literally a copy of the RAW rendered HTML from ASP.net (https://github.com/newjersey/dhs-oneapp-legacy/blob/master/NJOneAppAuto/Forms/Application/Confirmation.aspx.cs#L91).
  • This is not easy to replicate under the new API (since the API is not rendering HTML), and seems like a really bad user experience.
  • I'd recommend we just drop the confirmation email from the MVP scope at this time. If Protech would like to see an example of how to implement the confirmation email, we can design an email and use that instead of sending legacy HTML. <- Thoughts @allyceh?
• Updates docs to match all new queries / mutations.

[ronaldheft-gov]

Ready for review again. Planning on rebasing once all the existing PRs are merged in, because this we can test this end-to-end.

[ronaldheft-gov]

Merged in latest main. Running through a full end-to-end test.