De-migration Requests-Modernized Registry to COLIN

Central epic to capture and track all client de-migration requests to move an entity back to COLIN from the Modernized BC Registries platform (amalgamation, filing gaps, technical limitations or other business reasons).

Check/Eligibility for De-Migration from Modern to Legacy

- [ ] Business is originated in Colin
- [ ] Business was part of migration batch / business was migrated through the pipeline (validate in tracking tables)
- [ ] Business doesnt have excluded from colin sync filing filed at modern `excluded_filings = [
'lear_epoch',
'adminFreeze',
'changeOfLiquidators',
'changeOfOfficers',
'changeOfReceivers',
'courtOrder',
'noticeOfWithdrawal',
'registrarsNotation',
'registrarsOrder',
'transparencyRegister'
] and delay of dissolution`

Note : If Business has performed Alteration Filing in Modern (BEN to BC or BC to BEN) Colin wont be keeping any documents nor colin sync generates documents in Colin.

No files, tests, or entry points are named. Start by clarifying the de-migration workflow, reviewing the migration tracking tables and the listed eligibility conditions, and define the expected handling of excluded filings, dissolution delays, and altered businesses before implementation can be considered done.

Written by the indexing model from the issue text.