Support version argument when retriggering pull-from-upstream

[nforro]

In case of multiple release streams and pull-from-upstream configured for one of them (e.g. with upstream_tag_include/upstream_tag_exclude or version_update_mask), retriggering such job will work only if the configured release stream is the highest, because the version to update to is the highest retrieved from release-monitoring.org. I don't think it's possible to determine the correct stream from the configuration, so allowing users to specify the version when retriggering seems to be the only option to make it work for other streams.

[nforro]

This is a follow-up to #3024.

[lbarcziova]

I don't think it's possible to determine the correct stream from the configuration

can you clarify this please? Couldn't we just apply the configuration options from the particular job config for filtering of the versions from release monitoring?

[nforro]

Hm, thinking about it again, you are right, it should work, we can just apply the mask/rules to the list of all released versions and pick the highest one.