Expand order syncing to include more regions

[governmentSponsored]

User Story:

As a Data Verifier in the [some region], I want to be able to see transfers and consolidations for chapter 15, so that I can verify them.

Preconditions:

Precondition 1

Acceptance Criteria:

• Acceptance Criteria 1

Notes:

At a minimum we will have to sync chapter 15 orders for all regions since chapter 15 will be disabled in ACMS.

Currently we are limited to region 2 with only chapter 15 by default and chapters 11 and 12 controlled by feature flags.

We need to decide whether to sync all chapters for all regions and how far back in time to go and keep in mind that there will be consequences as to how long the sync takes and it potentially timing out and failing in a non-deterministic state.

Definition of Done:

• Acceptance criteria met - The system meets all acceptance criteria
• Feature toggles created - Features that are deployed but not released have toggles
• Design QA passed - All visual UI looks and works the way it’s supposed to
• Usability validated - Team ensures the working code is easy to use
• Accessibility tests passed - System passes automated and manual accessibility tests and supports applicable devices
• Code refactored for clarity - Developers can understand the work simply by reviewing the code
• Dependency Rule followed - More important code doesn’t directly depend on less important code
• Development debt eliminated - UX and code aligns to the team’s latest understanding of the domain
• Source code merged - Code has been merged into the main branch
• 90% unit test coverage achieved - Automated test coverage tools indicate coverage of >= 90%
• Code reviewed - Code is reviewed by at least two other team members before being merged
• Code quality checks passed - Code passes all automated quality checks
• Security scans passed - Code passes expected scans for vulnerabilities and compliance issues
• Threat model updated - The threat model incorporates new threats and remediations 
• Build process updated - Automated build process include code supporting the user story
• Load/performance tests passed - Performance tests include the functionality of the user story
• Documents are updated - All required documentation is up to date and version controlled
• Code is deployed - Code is deployed to the highest production like environment