convert-merge-rails --create-mr: always create MR for version branching point
Currently, if a topic brings in less changesets than --min-mr-weight
, the MR is not created.
This is fine, but in the case when the process stopped on a version branching point, the MR must be created nevertheless.
This is especially true because simply resuming will happily proceed to add more changesets that we do not want yet, since we are now past the branching point. This would not be a total disaster (if the branching point is published early, we can always tag it after the fact), but the new changesets can induce CI problems that make them harder to validate without changing things in the support infrastructure that we don't want to change until after the branching point.