feat(sdk.v2): Parse pipeline param in argument values

[chensun]

Description of your changes:
To support string concatenation in pipeline params, for instance:

@dsl.pipeline(name='pipeline-with-pipelineparam-containing-format')
def my_pipeline(name: str = 'KFP'):
  print_op('Hello {}'.format(name))

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

• Do you want this pull request (PR) cherry-picked into the current release branch?

  Learn more about cherry-picking updates into the release branch.

[google-oss-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun

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

The pull request process is described here

Needs approval from an approver in each of these files:

• sdk/OWNERS [chensun]

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

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chensun

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

The pull request process is described here

Needs approval from an approver in each of these files:

• sdk/OWNERS [chensun]

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

[neuromage]

Is this format for parameter name by convention? Should this be a shared method instead?

[chensun]

The naming here is only for one special scenario -- compiler injects an input parameter, which so far only happens in this specific code location. i.e. if it's extracted into a shared method, that method will only be called here. So probably not necessarily to make a method for this?

That said, there're two requirements for the naming conversion:

1. The name needs to be unique among all injected inputs for the current component. (This is guaranteed because param.full_name is unique)
2. The name also shouldn't collide with any existing user defined input for the current component.

I added some comments in the code, and changed to use double dashes to form the name, so hopefully it should rarely collide with user defined inputs. I also added a check, in case name collision happens, we at least throw an error here.

Of course, we can have some logic to iterate through all the existing input names, and always generate a unique name. But I feel it's a bit overkill, with the double dash and collision check, it should be good for most cases. WDYT?

[neuromage]

/lgtm