APPT-1663 - Persist the new session info when going back in the uplift journey

[ste-banks]

Description

We need to persist the updated session when hitting the 'go back' button in the journey but as the change session uplift journey doesn't use the wizard, I've had to implement this using session storage instead. The item will be removed upon submission of the session edit OR if going back as far as the edit session decision page. Existing unit tests have been updated to ensure the remove/set/get session storage methods get called where relevant.

The long term fix for this would be to refactor the change session uplift journey (and the cancel session uplift journey) to use the wizard steps but that change is too big to sort this bug fix out and we've had a number of issues around both of these recently, hence resorting to using session storage instead.

Fixes # (issue)

Checklist:

• My work is behind a feature toggle (if appropriate)
• If my work is behind a feature toggle, I've added a full suite of tests for both the ON and OFF state
• The ticket number is in the Pull Request title, with format "APPT-XXX: My Title Here"
• I have ran npm tsc / lint (in the future these will be ran automatically)
• My code generates no new .NET warnings (in the future these will be treated as errors)
• If I've added a new Function, it is disabled in all but one of the terraform groups (e.g. http_functions)
• If I've added a new Function, it has both unit and integration tests. Any request body validators have unit tests also
• If I've made UI changes, I've added appropriate Playwright and Jest tests
• If I've added/updated an end-point, I've added the appropriate annotations and tested the Swagger documentation reflects the change

[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