[RHOAIENG-6573] Model Detail - Registered Deployments Section

[jpuzz0]

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

Description

• Added labels to creation of model deployments
• Added registered deployments to model version details and archived model version details.

(cc @yih-wang)

How to test

Navigate to the version details of a given model version (archived or otherwise). Click on the registered deployments tab, verify the contents match the design in terms of the alert, table columns, and table data. If no table data exists, that means the version has no registered deployments, so you can create one using the toolbar action "Deploy".

Test Impact

Added unit tests and a cypress test verifying data can render in the registered deployments table.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• 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

[mturley]

LGTM at a quick glance - will do a more complete review tomorrow morning. Thanks for the work @jpuzz0 .

[yih-wang]

Thanks for the efforts @jpuzz0! One comment and two questions -

• The microcopy of the tab name and the alert should be aligned with what is provided in the handoff doc, reference this row
• I see a column for API protocol in the table on the live Model Serving page, but it doesn't show up in the screenshots, has that column been removed in the latest RHOAI version?
• I'm a little confused when I see the case that deployments are showing up for an archived version. Because the user is not allowed to archive the version/model which includes active deployments, so for an archived version, this tab should always be empty.

[jpuzz0]

• this row

@yih-wang

1. I've updated the microcopy

2. Your mockups don't have that API protocol column, so therefore I removed it for this instance of the table:

3. We currently don't have that restriction setup, and that isn't a part of this task's scope, so we can make a separate JIRA task/issue for that.

[mturley]

(tested for RBAC issues with an image on modelregistry-ui cluster after fetches were implemented, tested new changes on localhost)

[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