Race conditions when loading a draft registration

### Background
In many places in our apps, we let the users save a draft of a registration. If that registration contains information from another data entity that has its own life cycle, we need to check the validity of that data entity in the context of the draft registration before allowing the user to continue with the flow.

### Examples
**SP(DBA)/GP Example**
When filing a registration for a "Sole Proprietorship (Doing Business As)", the user will mention a business as the proprietor. That business is assigned to the SP(DBA) registration. If the user saves a draft of the registration and the mentioned business is cancelled or dissolved, when the user goes back to the draft SP(DBA) registration, the user needs to be prompted with that information.

This race condition can happen up to the point the payment is complete. I.e. Even if the information in the draft registration for SP(DBA) is up to date and valid, there is still a finite time before the payment is completed where the mentioned business can be cancelled or dissolved.

### Requirement Gathering Ideas
* What does the business do currently? (Need exhaustive list of scenarios)
* What does the business want to do currently?
* What are the implications (also frequency and severity) of finding an invalid filing today?
* What should we do in the new BC Registries?
* What can we do in the new BC Registries?
* Where does the priority for addressing this fall in relation to other commitments?

The issue names no files, tests, or entry points to inspect. Start by gathering the exhaustive business scenarios, implications, desired behavior, and priority listed in the requirement-gathering ideas; done would require an agreed approach for detecting and handling invalid entities throughout the draft and payment flow.

Written by the indexing model from the issue text.