Add info alert to kserve on settings page

[DaoDaoNoCode]

Closes #2047

Description

Previously, we only showed this alert when Multi-model serving platform was checked but unchecked later. In this PR, we apply the same behavior to Single model serving platform as well. No matter which checkbox was checked before but unchecked later, we show this info alert with the following text.

How Has This Been Tested?

1. Enable both single and multi model serving platforms
2. Uncheck either of them, but not both, see if the alert is showing

Test Impact

Add an integration test check to see if this alert also shows when single model serving platform was checked but unchecked later.

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]

@kaedward @vconzola Could you check the text in the alert here? The mockup only shows the alert text when we uncheck a multi-model serving platform, however, we want to apply the same behavior to the single model serving platform. Should we use a more general text as is shown in the description for both settings or do you have any better ideas to show a different alert text for the single model serving platform?

[lucferbux]

/lgtm

Let's wait for UX first

[vconzola]

@lucferbux @DaoDaoNoCode Is the scenario here that both boxes were checked and the user just unchecked multi-model serving? If so, I'd say some thing like, "Disabling multi-model serving means that models in new projects or existing projects with no currently deployed models will be deployed from their own model server. Existing projects with currently deployed models will continue to use the serving platform selected for that project." @kaedward - Please review.

[DaoDaoNoCode]

@vconzola It's the check for either checkbox. It also could be the user selected the single model serving platform before but unchecked it later, we also need to show the info alert, so we should either show a generic info alert for both situations or create different alert text for these 2 situations.

[vconzola]

@DaoDaoNoCode I think it would be better to have different alert text for each scenario. For the single model serving case I'd suggest something like, ""Disabling single model serving means that models in new projects or existing projects with no currently deployed models will be deployed from a shared model server. Existing projects with currently deployed models will continue to use the serving platform selected for that project." The italics just indicate changes from the multi-model use case text.

[kaedward]

@vconzola that sounds great!

[DaoDaoNoCode]

@vconzola Thanks for the suggestion! Could you check it again?

[vconzola]

LGTM.

[lucferbux]

/lgtm

[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