Change error when importing v1 pipeline

[DaoDaoNoCode]

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

Description

When importing a pipeline, do the following check:

• Whether there is an InvalidInputError in the error message
• Whether there is parsedYaml.kind === 'PipelineRun' && parsedYaml.apiVersion === 'tekton.dev/v1beta1' in the YAML file uploaded
  If true, then we change the error message to prompt user to the docs, and migrate their v1 pipelines to v2.
  NOTE: The docs are not available yet, it's for 2.17. So you will see 404 pages by clicking those links. But they are verified by the doc team.

How Has This Been Tested?

1. Import a v1 pipeline (I added the example into the cypress test, you can find it in the code changes)
2. Make sure you got the error message with links to the docs

Test Impact

Added cypress tests to verify this change

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign manosnoam for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• frontend/OWNERS

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

[DaoDaoNoCode]

@yannnz Could you review the screenshot? I changed the View documentation button to 2 link buttons because there will be 2 docs for self-managed services and cloud services. They share the same link with the argo error, so I just reused them.

[Gkrumbach07]

this looks good

/lgtm

we can wait for UX