Potential feature request: PipelineArgument dynamically derived from PipelineParameter

Hello,

I couldn't find a pre-existing issue or documentation on this topic. Is it possible to create pipeline parameters which are dynamically generated from the values of other PipelineParameters?

e.g. the below shows the basic scenario we're looking for.

```python

customer_project = PipelineParameter(name="customer_project")
publish_version = PipelineParameter(name="publish_version")

# following is generated from above pipeline parameters but can still be used as an argument in Pipeline Steps
input_data_parameter = PipelineArgument(name="input_data", value_spec="base_input/{param:customer_project}/{param:publish_version}/train")
input_data = (input_data_parameter, DataPathComputeBinding(mode='mount'))
...
train_step = PythonScriptStep(
...
inputs=[input_data]
)

```

Is there a better way to do what I'm trying to do here?

Currently we have some workarounds like have a "parent" PythonScriptStep which just handles submitting child runs, and generating the right paths from pipeline arguments, but it seems like an extra step and ability to have something like above would be nicer for us.

L’issue mentionne PipelineParameter, PipelineArgument, PythonScriptStep et DataPathComputeBinding, mais aucun fichier ni test. Commencez par consulter l’API et la documentation Azure Machine Learning concernant l’interpolation des paramètres dans les arguments, puis comparez le comportement proposé avec le workaround du PythonScriptStep parent ; le travail serait terminé lorsqu’une approche prise en charge aura été décidée et qu’un exemple ou une implémentation sera disponible.

Rédigé par le modèle d'indexation à partir du texte de l'issue.