Motivation / Background

Watermill currently uses an obsolete version of the Exponential Backoff Go Package. This upgrades Watermill from using v3 to v5.

This upgrade contains multiple breaking changes, but since the API is wrapped inside custom retry middleware we can hide these API changes from the user.

Detail

This requires moving from backoff/v3 MaxElapsedTime to a full backoff/v5 Retry implementation.

IMO, making the retry hook work here is a bit clunky since there is no native way of implementing it, and it needs to be hidden in the operation.

This also bumps the go version in go.mod up to 1.23

Alternative approaches considered (if applicable)

I am aware this conflicts with PR #564.

Happy to move forward with that PR instead if the community decides that is a better approach.

Please also provide feedback on my implementation! I have only been working with Go a few months.

Checklist

The resources of our team are limited. There are a couple of things that you can do to help us merge your PR faster:

• I wrote tests for the changes.
• All tests are passing.
  • If you are testing a Pub/Sub, you can start Docker with make up.
  • You can start with make test_short for a quick check.
  • If you want to run all tests, use make test.
• Code has no breaking changes.
• (If applicable) documentation on watermill.io is updated.
  • Documentation is built in the github.com/ThreeDotsLabs/watermill/docs.
  • You can find development instructions in the DEVELOP.md.