Support running image pipeline with parameters

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Being able to run an EC2 image pipeline, while overriding the parameters from the recipe, coming from the different components.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We have a setup where we need to build 200 images in the same way on a recurring basis, but only the hostname of the machine is different. We would like to supply that as a parameter to the image recipe, overriding whats maybe defined in the components. This way we don't have to build 200 image pipelines for each machine with a different hostname.

**Are you currently working around this issue?**
We are in the process of switching to EC2 image pipeline, but probably then indeed have to either create 200 pipelines + 200 recipes or create a single one and have it pull the hostname from a standard SSM parameter and change that with automation around it before we trigger the build. Both are not really nice ways to solve it .

Start by reviewing how EC2 Image Builder pipelines pass values through image recipes and components, focusing on overriding a hostname per run. Compare that with the mentioned workaround of reading an SSM parameter. Done means one pipeline can build multiple images while accepting run-specific parameter values without duplicating pipelines or recipes.

Written by the indexing model from the issue text.