LG-6348: Redirect user to "Ready to verify" page on completion

[aduth]

Why: So that a user who chooses to verify their identity in-person can be given instructions on how to complete the process in person.

This is meant to implement a basic scaffolding for the page of LG-6348, with actual page content to be built as follow-on work.

Testing Instructions:

1. Navigate to http://localhost:3000
2. Sign in
3. Navigate to http://localhost:3000/verify
4. Complete proofing flow up to document capture
5. Use error document to trigger error result
6. Click troubleshooting link to proof in person
7. Complete proofing flow
8. Observe page shown in screenshot below at end of proofing flow

Screenshot:

[aduth]

Alternatively, we could look for an enrollment for the user and use that as the primary indicator, if we think that's the better canonical source of truth. I expect we'll probably want to be tracking the proofing component regardless though.

[aduth]

I'm working on a local branch from this one to build out the rest of the content for this page, and we'll most certainly need to reference the actual enrollment record associated with this proofing attempt, so I'm thinking it'd probably be best to consider that value here. That being said, we don't actually create an enrollment yet, so maybe we should revisit that once we are.

@tomas-nava Do we have a ticket which captures the creation of the enrollment record?

[jmhooper]

+1 on using the enrollment. That does seem like a better source of truth

[sheldon-b]

Agreed, I think we should check the enrollment. I don't think there's a ticket yet for creating the enrollment

[aduth]

Based on my read of LG-6708 / #6556, the new "establishing" status looks like it'll be used so we can create the enrollment sometime early on in the flow. I think once we have that, I'll plan to update to reference the enrollment record. I'll leave some "WILLFIX" comments and can hopefully resolve it in one of the further iterations of the work of this ticket.

[aduth]

The new ticket LG-6868 will probably tie into this as well, since we'll need to consider the enrollment as part of updating the profile at the password confirmation step.

[aduth]

Admin merging due to ongoing GitLab issues (see Slack discussion).