fix(aci): fix metric detector charts

[mifu67]

Before:

After:

[sentry]

Bug: The timeWindowMs calculation is incorrect, making it 60 times smaller than intended, which will cause incident status areas to render at incorrect timestamps.
_{Severity: CRITICAL | Confidence: 1.00}

🔍 Detailed Analysis

The calculation for timeWindowMs was changed from snubaQuery.timeWindow * 60 * 1000 to snubaQuery.timeWindow * 1000. This change is incorrect because snubaQuery.timeWindow is in seconds, not minutes, and the timeWindowMs value is intended to represent a duration in milliseconds that was previously derived from a minute-based value. As a result, timeWindowMs will be 60 times smaller than expected, causing statusAreaStart and statusAreaEnd boundaries to be calculated incorrectly. This will lead to incident status areas being rendered approximately 60 times too early on the chart, making the visual representation misleading.

💡 Suggested Fix

Revert the change to timeWindowMs calculation at static/app/views/detectors/components/details/metric/charts/metricDetectorChartOptions.tsx:260 by restoring the multiplication by 60 to snubaQuery.timeWindow * 60 * 1000 to correctly convert the time window from minutes (as implicitly expected by the original calculation) to milliseconds.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location:
static/app/views/detectors/components/details/metric/charts/metricDetectorChartOptions.tsx#L260

Potential issue: The calculation for `timeWindowMs` was changed from
`snubaQuery.timeWindow * 60 * 1000` to `snubaQuery.timeWindow * 1000`. This change is
incorrect because `snubaQuery.timeWindow` is in seconds, not minutes, and the
`timeWindowMs` value is intended to represent a duration in milliseconds that was
previously derived from a minute-based value. As a result, `timeWindowMs` will be 60
times smaller than expected, causing `statusAreaStart` and `statusAreaEnd` boundaries to
be calculated incorrectly. This will lead to incident status areas being rendered
approximately 60 times too early on the chart, making the visual representation
misleading.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

_{Reference_id: 2633684}

[mifu67]

naur, I changed it BECAUSE it was rendering the status areas incorrectly.