Use sync preferred project when switching to global model serving page

[DaoDaoNoCode]

Closes #2137

Description

1. When you switch between the navs (projects, pipelines, model serving), the preferred project is always remembered and synced up
2. When you choose All projects on the global model serving page, the preferred project is set to null (We don't have that dropdown selection on the pipelines page)
3. Remove the filter label so you could select all the available projects on the global model serving page, but not only the dashboard projects
4. Fix some nits from Merge f/model-serving to main #2123

How Has This Been Tested?

1. Go to the projects page
2. Get into any project
3. Click on the model serving on the side nav
4. You should be able to land on the page with the same selection as the project you just entered
5. Go to the pipelines page, you can see the selection is kept
6. Select All projects on the global model serving page
7. Make sure everything works

Test Impact

N/A, this needs e2e test setup IMO.

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

[DaoDaoNoCode]

/hold
Do not merge until #2135 is fixed because this change will make the performance issue worse.

[andrewballantyne]

Conceptually this is fine by me...

There is a performance issue that will prevent me from approving here. It is a separate issue, but this will expose it more.

[lucferbux]

This approach is better, I'm gonna test it later with my fix to see if helps

[lucferbux]

/lgtm

[lucferbux]

/lgtm

[lucferbux]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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