Create dashboard configuration to control kserve and modelmesh

[lucferbux]

Description

Closes #1939 #1975

Create dashboard configuration to control kserve and modelmesh enablement as model serving platforms

Work In Progress I need to figure out the upgrade path of existing clusters

How Has This Been Tested?

There are two main paths to test:

Upgrade path from an existing dashboardconfig

1. Deploy and old dashboardConfig object which doesn't contain disableKServe nor disableModelMesh
2. Start the dashboard
3. Check that in the config response, the dashboard is returning the following: disableKServe: true and disableModelMesh: false

Upgrade in a fresh cluster

1. Deploy the latest CRD
2. Either delete the dashboardConfig CR object or just add whatever configuration you want with disableKServe and disableModelMesh
3. Check that in the config response, the dashboard is returning the following disableKServe: false and disableModelMesh: true

Refresh an actual configuration

1. Set up disableKserve: false and disableModelMesh: false
2. Check that it's returning the correct value

Test Impact

We don't have anything in place for the backend, we might need something in the future to cover migrations and so

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]

I still need to figure out the proper way to the migration path from existing clusters, this covers the newly created clusters, might need to add some migration in the backend, we can do that as a follow up.

[lucferbux]

I will continue the work and testuite for the migration here: #1975

[lucferbux]

@uidoyen If you can take a look at this too it would be amazing, thanks in advance!

[lucferbux]

Ok, got the migration path, we need to have test coverage for that in the future, I'm gonna start a talk about that to see what the team thinks.

[andrewballantyne]

Testing for this will be covered in other work. We need to verify testing infra is properly added to the backend... which may be in incubation at this point (I think it's part of the byon work if I recall correctly)

[DaoDaoNoCode]

/lgtm

[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