UI support for increased MultiHTTP, scripted and browser timeouts

[ckbedwell]

Problem

We are increasing the allowed timeout in scripted and browser checks to better support longer running checks. Currently the UI only allows these type of checks to timeout after up to a minute.

Acceptance criteria

(confirm confirmed with @d0ugal) -- all the below does also apply to MultiHTTP checks, as well.

1. Increase the allowed timeout for checks to 90 seconds. Please note that this will need to be incrementally bumped in PRs at a later date to match the rollout plan as discussed in this document
2. Add validation that the frequency can not be less than the allowed timeout. The minimum frequency for a browser / scripted check is 1 minute but as we will be increasing the timeout above this, we need to ensure that checks have the opportunity to cross-over as little as possible.
   • Display an error message beneath the frequency selector explaining it can not be less than timeout. They must adjust one or the other.
   • Do not automatically adjust the allowed frequency based on their timeout selection. We have to be explicit to the user in this scenario it is not allowed. If we adjust it for them it will be a source of confusion for the user that their desired frequency is not being honoured.
   • Ensure that the wizard form moves to step 5, displaying the error when the form is submitted from another step.
   • (confirm confirmed with @peterschretlen ) - Currently we allow timeout to be greater than frequency in the UI but the api rejects it. Please ensure endpoint checks are included in the validation.
3. Please ensure all the above has the correct integration tests added.