Release tooling: Keep redundant commits when cherry-picking

[JReinhold]

What I did

Adds the --keep-redundant-commits flag to cherry picking when picking patch PRs.

This ensures that it doesn't bail when trying to pick already picked PRs, such as those that have been manually picked previously, or where the "picked" label was not originally on for some reason.

We want to still cherry-pick and commit these commits so they get into the git history, and thus gets correctly labeled when publishing the version. If we instead chose to skip the commits, the labeler would not label such PRs as "picked".

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[kasperpeulen]

Nice!