fix(backend): parallelFor consume upstream inputs. Fixes #11520

[zazulam]

Description of your changes:

• Updated resolveUpstreamArtifacts to use getDAGTasks to allow for it parse through parallelFor DAG contexts to retrieve the appropriate producerTask. This fixes [backend] dsl.ParallelFor loop: cannot resolve the upstream artifact output of a previous pod #11520, it seems that the call with the filter to GetExecutionsInDAG was not reverted back to the same as it is in resolveUpstreamParameters in feat(backend): implement subdag output resolution #11196.

• Updated the argocompiler for the iteratorTask section. The additional "-loop" added to the task associated with the parallelFor DAG breaks the dependency validation that the argoworkflows API calls in the submission of the pipeline. This partially resolves [sdk] Unable to aggregate results over ParallelFor in Kubeflow V2 using V1 workarounds such as .after() #10050 for the .after() usage of a parallelTask. The implementation for dsl.Collected in the backend will be coming in a follow-up PR.

cc: @droctothorpe

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this 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 chensun 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:

• backend/OWNERS
• samples/OWNERS

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

[google-oss-prow]

Hi @zazulam. 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.

[droctothorpe]

/ok-to-test

[zazulam]

/retest

[zazulam]

Seems like this PR is also being affected by the flaky tests. I ran the failing pipelines locally and all passed.