Profile API misses error info of failed detector after result index rolls over

[yizheliu-amazon]

Issue:

Given detector fails initialization, Profile API returns error info like "all features are disabled". However, after a while, calling Profile API again won't return error info, only "Stopped" state.

Impact:

UX shows wrong state/message because of this. UX relies on the error info to show appropriate error message, and failure state. Detector failed initialization has "Stopped" state + error info, while normal "stopped" detector has "Stopped" state + empty error info. UX uses error info to show appropriate error state message.

Root cause:

This is because of that Profile API of AD plugin gets error info from .opendistro-anomaly-results index, which rolls over every 12 hours.