Review Code Review Requirements for Calls to MPI

[joeniquette]

slack conversation here: https://dsva.slack.com/archives/C019S3NSSAD/p1618239519148200 and here: https://dsva.slack.com/archives/CBU0KDSB1/p1618237577267200 and here: https://dsva.slack.com/archives/CBU0KDSB1/p1618234214257100

Essentially this ticket asks that we review all code changes/additions for calls to MPI through va.gov and ensure our team is alerted/forced to approve before the change can go to production.

• Check codeowners
• Help from Fleet has been offerered if we want to build in some regex checks that for reviews if certain keywords are mentioned.
• Document all places of concern in this ticket, create new tickets for each subsequent Change
• Eric Boehs has also offered help if we want to use something with Github Actions

If you are looking to dive into code review and github actions, this is the ticket for you.

[bramleyjl]

This issue is serving as a mini-epic for adding Identity as codeowners for the MPI lib, adding a validator for calls to the MPI service, and any other improvements to the data we send to MPI that might come up.

The MPI validation functionality is currently blocked pending detailed data specifications from MPI.

[bramleyjl]

MPI validation that is blocking this is planned to be completed in Sprint 53.

[bramleyjl]

MPI validation that is blocking this is planned to be completed in Sprint 54 in coordination with @lihanli .