chores<test>Improve integration test pipelines: add inputs, outputs, and multi-task chaining Fixes #12017

[devc007]

…

Description of your changes:
Fixes #12017

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. fixes chore(<test>): Increase integration test coverage by not relying only on pipelines based on container components #12017
• Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Hi @devc007. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[google-oss-prow]

[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 james-jwu for approval. For more information see the Kubernetes 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:

• OWNERS

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

[github-actions]

🚫 This command cannot be processed. Only organization members or owners can use the commands.

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

@devc007 can you please add Fixes #12017 to the PR description (first comment) so GitHub automatically closes the issue when this PR is merged?
More info: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword