Error using NR in OneStop if client changes NR from XPRO to BC

### ServiceNow incident:
INC0103824

### Ops report of bug

> **Session ID : 1723908**
> **NR# 5190144**
>
> Jamie is trying to register a DBA for her client who she previously registered an extra-provincial corporation in BC for. When she gets to the set to validate name request, she gets the error "System error occurred while retrieving the name request. Please try again later. If it keeps happening, please contact the OneStop Help Desk." There is no problem with the name request number that I can determine, and the parent corporation looks to be registered properly as well. No idea what could be causing this problem.

### Client's steps / Steps to replicate
1. Client requests a new NR, **XPRO** limited partnership
2. Client edits their draft NR to be a **BC** sole proprietorship
3. Examiner approves the NR
4. Client goes to use the approved NR on OneStop to register a BC Sole prop
5. Client gets an error, mismatched filing and NR.

Linda thinks the issue might be caused by XPRO collecting a home jurisdiction field, but when it turned into a BC name, the home jurisdiction number stayed in the BC NR, and OneStop doesn't know what to do with it.

### Chance of bug occurring
100% chance if a client changes their NR from XPRO to BC

### Impact of bug
Clients don't often edit draft NRs, and don't often edit from XPRO to BC.. this is the first one we have seen, i think!