Describe the enhancement requested

We use the archery release cherry-pick command during the Release in order to update the maintenance branch once it has been created in order to pick the individual commits that are tagged on JIRA with the corresponding version:
https://github.com/apache/arrow/blob/master/docs/source/developers/release.rst#create-or-update-the-corresponding-maintenance-branch

We should update the cherry-pick command to allow picking individual commits from GitHub issues that are Milestoned with the new version too otherwise we have to manually cherry-pick those issues from GitHub.

An example of execution (the local maint-11.0.0 branch is fake from maint-10.0.0):

$ archery release --jira-cache /tmp/jiracache cherry-pick 11.0.0 --continue
git checkout -b maint-11.0.0 master
git cherry-pick 9b23bc45778d9191b229b61c036bd348b1e11602
git cherry-pick 66874f5a075525dd440f4d60e0e54042dcbe71ad
git cherry-pick e0ca46598fbaba01afe2feef9eeb7385ddf95028

Those commits are tagged with version 11.0.0 on JIRA but are not on the branch, we should replicate that workflow with GitHub issues that are part of the milestone.

This is the main logic for which commits to pick: https://github.com/apache/arrow/blob/master/dev/archery/archery/release/core.py#L465-L488

Component(s)

Archery