fix(sdk): fix set_container_image within ParallelFor. Fixes #12413

[uzi0espil]

Description of your changes:

This PR fixes a bug in PipelineTask.set_container_image where dependencies from PipelineChannels (like PipelineParameter or upstream task outputs) were not correctly registered if they were partA of a formatted string.

The previous implementation only checked if the entire name argument was a PipelineChannel instance. It did not handle cases where channels were embedded within a string.

This PR introduces logic to:

1. Use pipeline_channel.extract_pipeline_channels_from_any(name) to find all PipelineChannel instances embedded in the name argument.
2. Iterate through the found channels.
3. Add each channel to the task's self._channel_inputs list.
4. Added a compiler test for testing set_container_image within a dsl.ParallelFor.

This ensures that all dynamic dependencies used to construct the container image name are properly registered, allowing the KFP compiler to build the correct task execution graph.

Which issue(s) this PR fixes
Fixes #12413

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:

• sdk/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 @uzi0espil. 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.

[hbelmiro]

/ok-to-test

[hbelmiro]

/ok-to-test

[uzi0espil]

/assign

[hbelmiro]

/ok-to-test