Support groups of release PRs

[MarcoIeni]

Motivations

While I prefer "release on every PR", I'm unsure if that will work with all of the libraries we are dealing with and we'd likely need to be able to release subsets as needed.

From #1019 (comment)

Solution

We could have a pr-group config in the configuration file, so that release-plz opens 1 PR for each group of packages. Dependent packages, even if not specified in the configuration, should be included in the pr as well.
This is similar to the grouped update feature of dependabot.

Notes

• Does the code assume that there's only one release pr at a time? Maybe the branch prefix should contain the group name of the pr. We could add the "group" to the pr_name context that will be added in Add configuration field to customize release PR name #1740 .

[jbr]

Would this also include a "one release PR for each workspace crate" or is that a distinct use case?

[MarcoIeni]

I guess you can define one group for each crate :)
Having one PR for each crate, seems like a use case that could be enabled by this feature. But release-plz automatically figures out the groups, instead having the user to specify them.

[epage]

This is proposing a static subset. The problem is that it isn't always static.

[MarcoIeni]

Feel free to write how you would implement this 👍

EDIT: do you want to specify which packages to update when creating the release pr? E.g. from the cli?