Keep up with midstream

[lucferbux]

Description

This PR intends to update the functionality of MR by updating the codebase with latest Midstream changes.

There are some UI inconsistencies that we'll need to tweak cc @jenny-s51

Please take a look at all the pages in the review.

Screenshots

How Has This Been Tested?

Updated all testing, both unit and integration. Tested manually too.

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.

If you have UI changes

• The developer has added tests or explained why testing cannot be added.
• Included any necessary screenshots or gifs if it was a UI change.
• Verify that UI/UX changes conform the UX guidelines for Kubeflow.

[Griffin-Sullivan]

One bug is if you are on the main page and select the drop down next to Register Model:

Clicking Register new version will take you to:

Seems like the call to register a new version will have no registeredModelId so it doesn't know where to register the version to.

[lucferbux]

One bug is if you are on the main page and select the drop down next to Register Model:

Clicking Register new version will take you to:

Seems like the call to register a new version will have no registeredModelId so it doesn't know where to register the version to.

After checking the code, it seems that this is a bug in midstream, i need to check it there but it seems that's the case.

[EDIT] Found the issue, and it was my fault, should silently fail the NotReadyError, I changed that in the first refactor, should stick to the logic in midstream, already fixed.

[alexcreasy]

Haven't reviewed the code but tested locally in kind and it works great!

Nice job!

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexcreasy

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:

• clients/ui/OWNERS [alexcreasy]

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

[alexcreasy]

As Griffen did a thorough code review and we've both tested it. merging.

/gtm

[alexcreasy]

/lgtm