pipeline scheduled toggle is disabled for schedules with an archived …

[pnaik1]

…experiment

https://issues.redhat.com/browse/RHOAIENG-10393

Description

In pipeline version schedules table, disable toggling when experiment is archived

How Has This Been Tested?

1. Create a schedule with an active experiment
2. Archive that experiment
3. Go to the pipeline version schedules table, and check that schedule, you can see the toggle button is disabled

Test Impact

added cypress test cases

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

[DaoDaoNoCode]

This is not the optimum solution and will create a lot of duplicated network calls.

1. In https://github.com/opendatahub-io/odh-dashboard/blob/main/frontend/src/concepts/pipelines/content/tables/pipelineRun/PipelineRunTableRowExperiment.tsx, we will make a call to fetch the experiment for each row already, we should look into extract that logic and make it reused by both the experiment column and the status toggle so that we can reduce the API calls, otherwise every row will make 2 same API calls to fetch the experiment.
2. The changes you made to useContextExperimentArchived hook will also produce some duplicated API calls on the experiment schedules pages, which is unnecessary. On the experiment schedules table, everything is under the experiment context, and we should make sure we don't make extra API calls for the experiment again and fetch all the information we need from the experiment context because all the schedules on that page are from the same experiment.

[DaoDaoNoCode]

Tested, works great
/lgtm

[Gkrumbach07]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DaoDaoNoCode, 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:

• frontend/OWNERS [Gkrumbach07]

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