OBSINTA-789: Sort alerts by start time

[falox]

Alerts were being sorted before filtering by the incident's time range, causing incorrect chronological order when some alert timestamps fell outside the range. Refactored to filter alerts first, then sort only the remaining alerts by their earliest visible timestamp.

Assisted-By: Claude

[openshift-ci-robot]

@falox: This pull request references OBSINTA-789 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Alerts were being sorted before filtering by the incident's time range, causing incorrect chronological order when some alert timestamps fell outside the range. Refactored to filter alerts first, then sort only the remaining alerts by their earliest visible timestamp.

Assisted-By: Claude

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[falox]

/cc @DavidRajnoha

[falox]

/label ux-approved

[falox]

/label qe-approved

[openshift-ci-robot]

@falox: This pull request references OBSINTA-789 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Alerts were being sorted before filtering by the incident's time range, causing incorrect chronological order when some alert timestamps fell outside the range. Refactored to filter alerts first, then sort only the remaining alerts by their earliest visible timestamp.

Assisted-By: Claude

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[jgbernalp]

/lgtm

[jgbernalp]

/override ci/prow/okd-scos-e2e-aws-ovn

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: falox, jgbernalp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jgbernalp: Overrode contexts on behalf of jgbernalp: ci/prow/okd-scos-e2e-aws-ovn

In response to this:

/override ci/prow/okd-scos-e2e-aws-ovn

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

@falox: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.