Add InvalidArgoDeploymentAlert component to AppRoutes

[Gkrumbach07]

closes: https://issues.redhat.com/browse/RHOAIENG-5296

Description

Adds a alert to the top of every page that can be dismissed (and stays dismissed) when the following are true:

• pipelines feature flag is enabled
• there exists a condition with the following c.type === 'CapabilityDSPv2Argo' && c.status === 'False' in the DSC

How Has This Been Tested?

You can add this mocked data to backend/src/utils/dsc.ts

diff --git a/backend/src/utils/dsc.ts b/backend/src/utils/dsc.ts
index eae01bc1..a5a7e81d 100644
--- a/backend/src/utils/dsc.ts
+++ b/backend/src/utils/dsc.ts
@@ -12,6 +12,26 @@ export const getClusterStatus = async (
   const result: DataScienceClusterKind | null = await fastify.kube.customObjectsApi
     .listClusterCustomObject('datasciencecluster.opendatahub.io', 'v1', 'datascienceclusters')
     .then((res) => (res.body as DataScienceClusterList).items[0])
+    .then((dsc) => {
+      return {
+        ...dsc,
+        status: {
+          ...dsc.status,
+          conditions: [
+            ...dsc.status.conditions,
+            {
+              lastHeartbeatTime: '2024-04-03T19:11:09Z',
+              lastTransitionTime: '2024-04-03T19:10:27Z',
+              message: 'Argo Workflow CRD already exists but not deployed by this operator',
+              reason: 'ArgoWorkflowExist',
+              status: 'False',
+              type: 'CapabilityDSPv2Argo',
+            },
+          ],
+        },
+      };
+    })
+
     .catch((e) => {
       fastify.log.error(`Failure to fetch dsc: ${e.response.body}`);
       return null;

Then try running with pipeline feature flag enabled and disabled. with it enabled and the mocked data, you should see the alert

Test Impact

no tests added

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 or cypress tests 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).
  @kywalker-rh

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]

Everything looks great, not the solution I had in mind but I see the value of having this kind of flexbility, just add some comments and it will be ready to go

[yannnz]

The name of "View details" should be "View documentation"

[jgarciao]

Beware this PR closes https://issues.redhat.com/browse/RHOAIENG-5296 (not https://issues.redhat.com/browse/RHOAIENG-4258) and that the product detected is Argo Workflows (with an s at the end)

[kywalker-rh]

@Gkrumbach07 Based on @jgarciao comment above, can you update "Argo Workflow" to be "Argo Workflows"?

Otherwise this looks good to me.

[lucferbux]

/lgtm

changes proposed from UX are implemented

[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