Detailed data verification for existing BENs

With major changes in the data model for the legal name work, there is a need to verify the data migrated from the old LEAR db in detail to ensure data integrity.

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

**TODOs**
Find some existing businesses in Dev or Test that exist in GCP LEAR db as well for the business type of interest. Ensure that you pick businesses that have lots of completed filing types and that your testing covers all the filing types available for the business type. Assuming the GCP LEAR db hasn’t been modified manually or via a filing after being migrated from OCP LEAR db.

Do the following for the businesses you have selected to test with:
- [ ] Compare current/active and historical data in GCP LEAR db matches data in Openshift LEAR db.
- [ ] verify record values are same in tables. tables and fields are not a 1-1 mapping so that will need to be taken into account
- [ ] verify timestamps match
- [ ] 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 selecting existing businesses in Dev or Test that appear in both the GCP LEAR and Openshift LEAR databases, including businesses covering all relevant filing types. Compare active and historical table values and timestamps while accounting for non-matching table mappings and the different versioning approach; done means the selected data is verified for integrity.

Written by the indexing model from the issue text.