fixes sorting of Alert Instance in Details page

[gmmorris]

Summary

closes #80014

Sorts Alert instances by their status to ensure Active come first.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[gmmorris]

Ideally we'd sort this on the server side, but as we don't so server side pagination and we return an object rather than an array, making that change here would be much bigger.

With that in mind this is a minimal 7.10 fix design to address the localized bug and we'll address the broader aspects of this once we align with Design on this.

[YulNaumenko]

I agree that approach for getting instances from API should be changed in the future releases, because having it as an object complicates a bunch of things (like sorting, filtering, pagination, etc.). At least we discussed example for Maps alerts where it could be thousands of instances and they were asking me about possibility to navigate throw them with filters and sorting. It would be awesome @gmmorris if you will create a follow up issues for this if we don't have yet.
But for 7.10 current quick fix is LGTM and works as expected locally.

[gmmorris]

@elasticmachine merge upstream

[gmmorris]

It would be awesome @gmmorris if you will create a follow up issues for this if we don't have yet.

I'm surprised I can't find an existing follow up issue for the Alerts Detail page. @mikecote any ideas? Am I missing an existing issue?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: bcbc811

Metrics [docs]

async chunks size

id	before	after	diff
triggersActionsUi	1.5MB	1.5MB	+337.0B

History

• 💚 Build #80952 succeeded 323a9a3

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[ymao1]

LGTM

[pmuellr]

merged before I could review :-) ; LGTM, tried it with my simulator bits, worked as expected

[mikecote]

It would be awesome @gmmorris if you will create a follow up issues for this if we don't have yet.

I'm surprised I can't find an existing follow up issue for the Alerts Detail page. @mikecote any ideas? Am I missing an existing issue?

As discussed offline, there's no issue that I recall so worth opening one.