[ML] Fix formatting of values for time of day or week anomalies

[peteharverson]

Summary

Fixes the formatting of actual and typical values in the anomalies table for time_of_day and time_of_week detectors.

Fixes two issues:

1. Times are formatted in 24 hour format where before 12 hour format was incorrectly being used
2. Dates / times are formatted taking into account that the anomaly values are the offset in seconds from the UTC start of the day / week.

The values are formatted by using the timestamp of the anomaly, working in UTC, then get the start of the day / week in UTC, add on the offset value in seconds, and finally format in HH:mm or ddd HH:mm format using the configured Kibana timezone.

Before (anomaly time is 22:00, but actual in table is shown as 11:02 - one hour out and 12 hour format)

After (anomaly time is 22:00, and actual correctly displayed as 22:02)

Checklist

• This was checked for cross-browser compatibility, including a check against IE11
• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This includes a feature addition or change that requires a release note and was labeled appropriately

Fixes #32023

[elasticmachine]

Pinging @elastic/ml-ui

[jgowdyelastic]

LGTM

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[peteharverson]

retest

[walterra]

LGTM

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[alvarezmelissa87]

Bit late on this but LGTM!