Add deployment to global view and fix status

[lucferbux]

Description

Closes #1956

How Has This Been Tested?

No projects

1. Delete all projects
2. Go to model serving global
3. Check that the No data science projects view is rendered

Wrong project

1. Go to model serving global
2. Add to the URL modelServing/<path-to-wrong-object>
3. Check that the Project not found image is rendered

No models deploy in a new project

1. Go to model serving global
2. Select a newly create project with no serving platform selected
3. Check that you get the "no deployed model" view

Deploy a model in modelmesh

1. Create a new project and select modelmesh as the serving platform
2. Go to model serving global
3. Click Deploy model
4. Check that the modelmesh modal is shown

Deploy a model in kserve

1. Create a new project and select kserve as the serving platform
2. Go to model serving global
3. Click Deploy model
4. Check that the modelmesh modal is shown

List all resources

1. Go to model serving global
2. Check that you render all the resources

Filter by project

1. Go to model serving global
2. Filter by project
3. Check that only the right resources are rendered in the table

Test Impact

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 tests & storybook 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 (find relevant UX in the SMEs section).

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

[lucferbux]

@vconzola can you take a look at this please?

[DaoDaoNoCode]

/lgtm
Peer coding with @lucferbux and running everything.

[lucferbux]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DaoDaoNoCode, lucferbux

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 [lucferbux]

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

[vconzola]

@lucferbux A few comments...

1. For the "No models deploy in a new project" scenario, is this behavior consistent with the way pipelines handles the same scenario? It should be.
2. I think we need an additional empty state for the case where there the user has selected a serving platform for a project but hasn't deployed any models yet. We should show an empty state within the table with a deploy action button. (This might be handled automatically for our tables already?)