## Summary

Closes elastic#256735

This PR updates the RedirectWithDefaultDateRange guard in APM to improve
how we handle invalid and unexpected values in time range parameters for
URLs in APM that require said parameters.

## Root cause

A fair amount of routes in APM require a time range to be defined in the
query params of the url. Without them, the components rendered within
this routes wouldn't work properly and would instead throw errors that
would lead to a page crash. To avoid crashing because of this, the APM
app route has a built in guard in one of the wrapping components
`RedirectWithDefaultDateRange`. This component runs some validations
internally to verify that the time range parameters (`rangeFrom` and
`rangeTo`) are set. If any of the params are detected missing, the
component stops the rendering tree (returns `null`) and performs a
redirect ensuring the both parameters are set with defaults values in
case they're missing.

While this approach ensures a time range is set in case it is missing,
it wasn't factoring in that the parameters could be present but have
invalid values. Because up until now we were just checking that range
parameters had a string value, but weren't validating the string
content, the guard would allow rendering to continue but the unparseable
value would still trigger an error in the components downstream, leading
to a page crash.

The changes introduced in this PR update the validation run in the guard
component to verify not only that the parameters are set but also that
their values are valid, parseable datemath expressions. If one of them
(or both) aren't parseable, the redirect will be performed setting them
to whatever the default value for them should be. This ensures that a
valid time range is always available for components that expect it, both
when the range is missing or when it is present but invalid

## Reproduction
Navigate to the following path
`app/apm/services?comparisonEnabled=true&environment=ENVIRONMENT_ALL&rangeFrom=invalid&rangeTo=invalid&offset=1d`
verify how the page doesn't crash and the `rangeFrom` and `rangeTo`
values are replaced with valid default values. Defaults depend on kibana
settings, but the standard defaults are `rangeFrom=now-15m&rangeTo=now`

## Release note

Fixes an issue in APM apps where the website would crash if invalid
values were passed to rangeFrom and rangeTo query parameters in the URLs

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
(cherry picked from commit 58d2002)