[RHOAIENG-3887] Run Schedules - UX cleanup

[jpuzz0]

Closes: RHOAIENG-3887

Description

Added actions to the pipelines list, pipeline version details, wrapped Schedule settings in a form section for the Create/Schedule run page so that it can be jumped to.

Create run alert
https://github.com/opendatahub-io/odh-dashboard/assets/96431149/d0404281-a77a-42c3-9d22-7acc680a4181

Create schedule alert
https://github.com/opendatahub-io/odh-dashboard/assets/96431149/e07ab74a-9ded-4f93-9cfb-d317a5457f01

Pipeline version detail actions
https://github.com/opendatahub-io/odh-dashboard/assets/96431149/5731087e-a970-4070-b133-1522b7404aac

Pipeline list actions
https://github.com/opendatahub-io/odh-dashboard/assets/96431149/96fbdca8-b1a8-4e5a-96a5-db76c17ebddf
https://github.com/opendatahub-io/odh-dashboard/assets/96431149/6eb52b23-a022-480e-bd94-0e2314bad952

How to test

The videos above represent how one would test these changes. cc @yannnz

How Has This Been Tested?

Mostly manual testing, added some unit tests

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]

Can you add tests for the redirect like how juntao did in his latest PR:

it('navigate to create run page from pipeline row', () => {
     ...
    pipelinesTable.findRowByName(initialMockPipeline.display_name).findByText('Create run').click();
    verifyRelativeURL(`/pipelines/${projectName}/pipelineRun/create`);
  });

[jpuzz0]

Can you add tests for the redirect like how juntao did in his latest PR:

it('navigate to create run page from pipeline row', () => {
     ...
    pipelinesTable.findRowByName(initialMockPipeline.display_name).findByText('Create run').click();
    verifyRelativeURL(`/pipelines/${projectName}/pipelineRun/create`);
  });

Added these tests in latest commit.

[Gkrumbach07]

wait also found something else here

view runs for the version row does not apply the filter

edit: this also happens from the pipeline details screen too

[jpuzz0]

wait also found something else here view runs for the version row does not apply the filter

edit: this also happens from the pipeline details screen too

@Gkrumbach07 Ah, probably a consequence of some of the recent route changes from upstream. I'll take a look, thanks.

[jpuzz0]

wait also found something else here view runs for the version row does not apply the filter
edit: this also happens from the pipeline details screen too

@Gkrumbach07 Ah, probably a consequence of some of the recent route changes from upstream. I'll take a look, thanks.

FWIW, "View runs" wasn't a part of this PR, so this is a bug that already exists, but I'm still looking into it.

[Gkrumbach07]

This looks good, once tests pass we should merge

[Gkrumbach07]

Sweet tests pass, and the view runs bug has been fixed.
/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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