Fix issue when selecting a pipeline without version on the clone run page

[DaoDaoNoCode]

JIRA: https://issues.redhat.com/browse/RHOAIENG-4258

Description

When switching to a pipeline that contains no versions in it, we always trigger the hook useUpdatePipelineFormData and set the version to the incorrect one. The solution is to add a check before setting it to make sure we are only doing this when setting the same pipeline but not switching to another.
Also, fix a small issue that could crash the page.

How Has This Been Tested?

1. Create 2 pipelines (pipeline 1 and pipeline 2)
2. Delete the version in pipeline 2, make sure there is no version in it
3. Create a run using pipeline 1
4. Duplicate this run, and switch the pipeline selection to pipeline 2
5. Verify the version selector is disabled and showing "no versions available" in it

Test Impact

Add some conditions in the cypress test to verify the change works.

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]

tested live and works. low impact -- very nice. good stuff.

/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