[FUTURE] Dissolutions - Data Migration / Data Sync - Exclude Status Updates to COLIN for Corps in D1* / D2*

**Summary:**
- For MVP release BCROS will manage BC Corps including Dissolution processes
- For MVP release COLIN will continue to manage XPRO corps including Dissolution processes
- We need to ensure that the BCROS -> COLIN data sync does not update statuses for BC corps in COLIN in such a way as to trigger duplicate Dissolution actions on both systems
-
**Background:**
- We are currently investigating options for modifying the COLIN Dissolution jobs to exclude corps in conjunction with data migration of all in-progress Dissolutions to BCROS. One option being considered is to at the time of data migration change all D1* / D2* statuses to corresponding statuses with a 'P' prefix (_see below for proposed mappings_)
- For this approach to work we will need to ensure that the BCROS -> COLIN Data Sync process does not update/overwrite any corps in the COLIN DB which have a P1* / P2* status

**Other Approaches:**
- Alternative approaches to manage the parallel operation of the Involuntary Dissolution jobs are being investigated, if adopted they may require similar data safeguarding against inadvertent updating by the data sync process

**Proposed Mappings:**
D1A -> P1A
D1F -> P1F
D1T -> P1T
D2A -> P2A
D2F -> P2F
D2T -> P2T

Start by tracing the BCROS-to-COLIN data sync and reviewing the proposed D1*/D2* to P1*/P2* mappings. Confirm which COLIN records must be protected from status updates, and define done as preventing duplicate Dissolution actions while the alternative approaches remain under investigation.

Written by the indexing model from the issue text.