LG-11463 idv_session methods for phone step started, complete, invalid

[soniaconnolly]

🎫 Ticket

LG-11463

🛠 Summary of changes

Add idv_session methods to mark phone step started (user passed lexis_nexis in phone_controller), mark it complete (user entered correct code in otp_verification_controller) and mark it invalid (user just submitted request for a code, starting background job to query lexis_nexis).

We mark the phone step invalid at the beginning of create to follow the same pattern as the verify_info_controllers. We clear prior attempts at the beginning, and then the background job marks the step complete when it succeeds.

📜 Testing Plan

• Primarily specs, since this is refactoring
• Create account, start IdV
• Try to jump ahead to /verify/phone before submitting verify info, expect to remain on current page
• Try to jump ahead to /verify/phone_confirmation before submitting verify info, expect to remain on current page
• Try to jump ahead to /verify/phone_confirmation from phone page before clicking submit, expect to remain on phone page
• Enter correct code, expect to proceed to enter password
• Try clicking browser back button, expect to go back
• Resubmit phone page and enter correct code, expect to proceed to enter password

[matthinz]

LGTM