[RHOAIENG-4727] Compare runs - Parameters expandable section

[jpuzz0]

Closes: RHOAIENG-4727

Description

Compare runs - Parameters expandable section renders runtime config data associated with all selected runs from the Run list, where if a run does not share a parameter with another, empty cells are shown. The feature has a switch that allows for showing and hiding of parameter rows based on whether rows possess all of the same value. When row data extends beyond a certain point, horizontal scroll will kick in and the first column representing parameter names will stick while scrolling left and right.

NOTE: The design diverged slightly from what the mocks show at the moment. The implementation here is what was recently agreed upon with @yannnz.

Only showing parameters with values that differ between runs

Empty state

How Has This Been Tested?

Added cypress tests demonstrating interactions between the Run list and Parameters tables, along with hiding of parameters with values that are all equal.

How to test

Navigate to the Compare runs page /experiments/jps-fun-world/85c9d729-bf63-441f-af87-d6898e5db5f0/compareRuns?runs=[your list of runs here], verify the table design and interactions with the Run list above it.

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).

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

[Gkrumbach07]

code looks good besides the question on background color. will test it locally tomorrow

[Gkrumbach07]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gkrumbach07

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 [Gkrumbach07]

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