Detailed data verification for new SPs

With major changes in the data model and major code updates for the legal name work, there is a need to verify new business data created & updated in GCP.

In this ticket, we will verify data at the database level.

Note that SPs have the following scenarios that need to be verified:
* SP Individual
* SP LEAR DBA
* SP COLIN DBA

**TODOs**
- [ ] Create business type of interest by filing a IA or registration filing in GCP to completion.
- [ ] File all available filings for a given business type, eventually ending with a voluntary dissolution filing. Some of the filing types may require you to login as a staff user. Reference allowable actions document to determine what filing types should be tested for a given business type
- [ ] Verify the expected database records are created and populated with expected values
- [ ] Verify versioning of data is correct. Versioning approach is different in new GCP LEAR db so ensure you understand the differences. For example, the history table does not store a copy of the changes made in the active table in the history table which the previous versioning approach did.

Start by reviewing the three SP scenarios—Individual, LEAR DBA, and COLIN DBA—and the allowable actions document referenced in the TODOs. Create the specified filings in GCP through completion, then inspect the database records and versioning behavior in the new LEAR database; done means expected values and version history are verified for each scenario.

Written by the indexing model from the issue text.