Improve manual forward port jobs

[xmo-odoo]

Complements #1051

Currently if there are issues with forward ports I create forward port batches by hand, however this is a very raw / low level job, and creating objects by hand does not necessarily uphold all the implicit invariants which can cause issues:

• When trying to force a followup, if there are detached forward ports triggering from the source batch seems to not work, might need to find the latest forward port on the sequence (which might be on the branch we just disabled)

• If a batch keeps failing e.g. because it's a duplicate and the previous version is already merged the fw will keep trying and failing forever.

  • Might be a good idea to add some backoff.
  • Make into mail.thread and add failure note so the information is not hidden in the logs.
  • Maybe add more extensive backoff on failure (not just a constant backoff).

• Can create a double port via batches, not entirely sure how (probably because duplication is checked before creating the batch, once the batch is created there's basically no check)

• Maybe create a "force port" action on the PR which can do all the right things and we stop creating forwardport batches by hand?