Make MR Degrading status more prominent

[manaswinidas]

Part of RHOAIENG-15587

Description

The Degrading status wasn't visible at first, found during QA verification of RHOAIENG-15587

How Has This Been Tested?

The Degrading state usually appears for a very short period while deleting resources related to a specific MR. There is high possibility of not seeing this state unless you have issues during deletion. To simulate this state, add finalizers to any MR resource using OpenShift Console and try deleting the same MR via Dashboard, you should see the Degrading status.

Test Impact

Tests already covered.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• 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.

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

[mturley]

LGTM, thanks @manaswinidas

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mturley

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:

• frontend/OWNERS [mturley]

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