API - Modify order of assigning DB2 MHR number until after pay api request

[mstanton1]

In MHR currently the DB2 MHR number is assigned prior to the pay api request. As a result, if the pay api request fails the MHR number that was used in the request is skipped over. Staff have identified concerns with skipping numbers in the decal sequence, and the costs associated with purchasing decals that may need to be shred. This is to request the order be modified so that the DB2 MHR number is requested after the pay api request.

Developer Note:

1. Update new MH registration transaction management to request the next MHR number after a successful payment request.
2. Allow staff post-migration to manually enter an MHR number when creating a new MH registration. The MHR number must be both less than the existing maximum MHR number and not already used. This enhancement will allow staff to retroactively fill a gap in the MHR number sequence if one is detected.

To test, verify create registration still works for:

• New MH registrations
• Transfers
• Notes
• Cancel Notes
• Exemptions

[chdivyareddy]

Transfers and Exemption submission is currently being blocked in DEV, will verify those flows once the fix is in DEV.

[chdivyareddy]

All the registration filings listed above works in DEV.