Add KFP V1 Pipeline Test to CI Workflow

[kunal-511]

✏️ Summary of Changes

Added KFP v1 SDK (>=1.8.22,<2.0.0) pipeline test to CI workflow
Create simple hello world V1 pipeline test script

✅ Contributor Checklist

• I have tested these changes with kustomize. See Installation Prerequisites.
• All commits are signed-off to satisfy the DCO check.
• I have considered adding my company to the adopters page to support Kubeflow and help the community, since I expect help from the community for my issue (see 1. and 2.).

---

You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

[juliusvonkohout]

Thank you @kunal-511 .

1. I also think that the v2 pipeline test is still somewhat unstable. Can you make it more robust / deterministic in a separate PR ? Also in tests /gh-actions.
2. We should change the naming scheme so spark_install, spark, test, kserve_install, kserve_test etc. such that /tests/componentName_{install.sh, test.sh, test.py, test.yaml} for all files. Also the https://github.com/kunal-511/kubeflow-manifests/tree/add-kfp-v1-pipeline-test/tests/gh-actions/kf-objects files can be split up to be next to the other files per component. Lets also get rid of the tests/gh-actions and just have the files directly under /tests
3. https://github.com/kubeflow/manifests/blob/master/scripts/trivy_scan.py also belongs to /tests

Please split this up in separate PRs

[juliusvonkohout]

/lgtm
/approve

please continue with #3127 (comment)

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: juliusvonkohout

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [juliusvonkohout]

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