Detailed output 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 by comparing outputs generated by the legal api in OpenShift and the ones generated via GCP legal api. There are tickets to verify data at the database level already but this will serve as another check to surface data or output generation logic.

**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:
- [ ] Verify ledgers items match
- [ ] For each ledger item/filing, download and compare outputs between Openshift and GCP
- [ ] Create a bug ticket for specific output issues

Start by selecting existing businesses in Dev or Test that also exist in the GCP LEAR database, prioritizing businesses with many completed filing types. Use the legal APIs in OpenShift and GCP to verify ledger items and compare downloaded outputs for each filing type. Record specific output discrepancies as separate bug tickets and complete the checklist for the selected business type.

Written by the indexing model from the issue text.