Fix chart range bug of non-HC anomaly and feature charts

[ohltyler]

Signed-off-by: Tyler Ohlsen ohltyler@amazon.com

Description

Fixes a bug in the non-high-cardinality scenario where anomaly and feature charts were showing the explicit range based on the timestamps of anomaly results found in the parent date range, rather than showing the static date range itself. (see #121 for details/screenshots).

This fixes that bug by 2 main changes:

1. Explicitly setting the range of x values for the chart via xDomain chart prop for both anomaly details and feature charts
2. Splitting up the logic for HC and non-HC results, when the zoom range is changed. For example, in the non-HC scenario, if the zoom range is changed, we want to update the parent date range (as shown in the date range picker). In the HC scenario, we only want to change the range shown on the child charts, and not on the parent date range (if we change the parent date range here, then any selected heatmap cell would be de-selected, and the entire heatmap would be re-generated based on the new date range, which we don't want).

Confirmed everything works as expected for non-HC, single-HC, and multi-HC, for both RT and historical results.

Issues Resolved

Closes #121

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[ohltyler]

an error will be thrown if we set an xDomain in the aggregate anomalies case, since the scale type (see lines 633-635) won't work properly in the ScaleType.Ordinal type