[RHOAIENG-7485] Admin - Database status in Model Registry Table

[jpuzz0]

https://issues.redhat.com/browse/RHOAIENG-7485

Description

Show various statuses depending on model registry conditions within a new column labeled "Status" for the model registry list table page.

Degrading popover

Unavailable with multiple messages

(cc @yih-wang)

How Has This Been Tested?

Manually tested with sample data, created unit tests with possible status scenarios

Test Impact

Added unit tests

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[yih-wang]

We should use the Alert popover to display messages. Use variant Danger for Unavailable and variant Warning (or possibly Custom if the warning icon is hard-coded) for Degrading.

[jpuzz0]

We should use the Alert popover to display messages. Use variant Danger for Unavailable and variant Warning (or possibly Custom if the warning icon is hard-coded) for Degrading.

@yih-wang Updated. I've also updated the screenshots in the description.

[mturley]

Just one small nit, everything else LGTM

[mturley]

LGTM! Thanks for the help!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mturley

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:

• frontend/OWNERS [mturley]

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