When agentic tool triggers release pipeline, it should review templateParameters and select the correct package

Release pipeline in Java can contain multiple packages from a same service, e.g. [containerregistry](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/containerregistry/ci.yml) contains 1 data-plane package and 2 control-plane packages.

I was told by containerregistry service, that agent triggers the release pipeline when they intended to release `azure-resourcemanager-containerregistry-tasks` package (1 of the 3). But the pipeline didn't set the correct package. It uses the default configure. The result is the release pipeline runs on the wrong package, and it fails at the last step of checking SDK version in CHANGELOG (as the wrong package does not have expected CHANGELOG for release).
-- as the pipeline is triggered by agent, service dev does not have a chance to review that selection
https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release?tabs=releaseplan

PS: there is a reason for having multiple packages in the same CI. E.g. for storage data-plane lib, their packages have dependencies and need to be released together. (though there is less reason for control-plane lib to depend on another)

PS: for reference, we dev typically use this word to agent to let it run the release pipeline with correct parameter
```
2. Run the pipeline
- If the pipeline has "templateParameters", set the parameter of "release_{sdk-package}" to "true", all other parameters to "false"
- If the pipeline has no "templateParameters", just run it without parameters
```

Start with the linked containerregistry ci.yml and the release-pipeline documentation. Trace how agent-triggered runs discover templateParameters and select a package. Done means the intended release_{sdk-package} parameter is enabled, other package parameters are disabled, and the pipeline validates the selected package's CHANGELOG.

Written by the indexing model from the issue text.