Add test for CSRF error with different Person Escort Records in different tabs

[teneightfive]

Problem

There was an issue with frequent CSRF errors being logged within the Person Escort Record journeys.

The fix was to give a unique name to each form wizard instance so that if a user opens an old PER in another tab and tries to go back and submit the new PER they won't see a CSRF error.

Solution

We need to write an e2e test to ensure that this behaviour is still supported.

Test steps:

• start new PER
• enter any step of new PER
• visit old PER summary page for same section in new tab
• open previous tab and attempt to submit step
• should not receive CSRF error