Update /support page

[jakecosgrove]

Description

This PR updates the content on the /support page to make it shorter and more clear for users. A drop down details component has been added to the page to give users the relevant contact information if they need support outside of office hours.

Context

This content request was made by Callum Hemming on the behalf of the support team to try close gaps in onboarding and service information.

Some more work is needed on major incident processes and how far we need to expose this to our users.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[emmagifford]

2i checks complete. This updated content is clear and concise. Headings and links all look fine. The contact details in the details component look good. Happy to approve!

[emmagifford]

My 2i comments from earlier still stand, but the automated checker didn't like the use of bold for emphasis on 'NHSE National IT Service Desk' in the details component.

Jake's changed this to a H3 as it's under a H2 section. Checked this - looks fine.

There's nothing on using headings in a details component in the service manual, so we've presumed it should be okay. Also worth noting that Alex said a screen reader wouldn't read out the H3 if the component is closed.