Bug: Find the discrepancy between what's logged in rdm_records_state.json and rdm_records_dump.json

[sakshamarora1]

For example, staff association had 3394 records migrated
and toggling view all versions gave 3491 records while the json files have different numbers.
needs to be investigated

sh-5.1$ wc -l /migration/logs/staff_association/rdm_records_state.json
3337 /migration/logs/staff_association/rdm_records_state.json
sh-5.1$ wc -l /migration/logs/staff_association/rdm_records_dump.json
3338 /migration/logs/staff_association/rdm_records_dump.json
sh-5.1$ wc -l /migration/logs/hr/rdm_records_dump.json
861 /migration/logs/hr/rdm_records_dump.json
sh-5.1$ wc -l /migration/logs/hr/rdm_records_state.json
861 /migration/logs/hr/rdm_records_state.json
sh-5.1$ wc -l /migration/logs/thesis/rdm_records_state.json
11516 /migration/logs/thesis/rdm_records_state.json
sh-5.1$ wc -l /migration/logs/thesis/rdm_records_dump.json
11520 /migration/logs/thesis/rdm_records_dump.json

[sakshamarora1]

Probably related to #565

[sakshamarora1]

List of legacy recids and their corresponding versions where the files were fixed

legacy_recids_fixed.txt