PYIC-8615: Avoid a dead end for COI users - new app no-match screens

[AmritSidhu]

Proposed changes

What changed

• Add two dynamic version of this page with the context 'coi' & '6mfc'

Why did it change

• When users are routed to the new “We need more information to confirm your change of details” page (introduced in Part 1 (ticket# 8603) for 6MFC and COI journeys) and choose the passport via app option, they are taken into DCMAW and the GOV.UK One login app.
  In these journeys, users can drop off or fail at different points. To ensure consistent handling, dynamic routing has been introduced and 2 new variants of existing page /pyi-no-match -‘Sorry, we can not confirm your identity’ have been introduced

Issue tracking

• PYIC-8615

Checklists

• READMEs and documentation up-to-date
• Browser/ unit/ Selenium tests have been written/ updated
• No risk of exposure: PII, credentials, etc through logs/ code
• Ensure added/updated routes have CSRF protection if required

[blakeyp]

@AmritSidhu do the snapshots need regenerating? some still have the old naming?

[AmritSidhu]

@AmritSidhu do the snapshots need regenerating? some still have the old naming?

They need manually deleting, will do that

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud