feat: nested error discovery in check form

[ckbedwell]

Problem

As noted in the check form redesign work, this is required to help with error discovery: #847

With the wizard form pattern and now with the request components, it means that users may have difficulty finding errors to correct when submitting check creation / updates.

Solution

Add methods and event listeners which respond to an invalid check form submission. Because of the nature of the individual components which need to respond to the invalid submission it doesn't make sense to rearchitect them to respond via prop drilling or some overarching context. I have chosen to do this a little bit more vanilla with dispatching a custom event, setting up event listeners for the custom event and utilising useImperativeHandle where appropriate.

I have added test coverage for each of the check types which is doing a single spot check that the field with an error is being navigated to. I did have checks ensuring the input field was receiving focus but I have had to remove them as they were proving a little flaky in the CI/CD. I have left two specific focus checks for the script and probe fields as they are special and need to handled differently to all other form inputs.

Http check error discovery

Screen.Recording.2024-07-17.at.11.39.48.mov

Multihttp check error discovery

Screen.Recording.2024-07-17.at.11.44.00.mov

Script check error discovery, redirecting back to script tab from examples

Screen.Recording.2024-07-17.at.11.45.25.mov

Focussing probes select correctly when it has an error and is the first field

Screen.Recording.2024-07-17.at.11.46.59.mov

[VikaCep]

👏 👏 👏 👏

The base branch was changed.