Get MiMa running again

[rossabaker]

There is a step in the workflow to run MiMa, but it doesn't have any previous versions, so nothing is being checked. The addition of new abstract methods to various algebras, along with some changes in types, means not all 1.x releases are compatible. This PR establishes a new baseline of compatible versions:

• redis4cats-core: 1.7.1
• redis4cats-log4cats: 1.4.3
• redis4cats-effects: 1.7.2
• redis4cats-streams: 1.7.2

[yisraelU]

@rossabaker 🙏 TY, much appreciated. this has been on my todo list for too long

[rossabaker]

Since bincompat has already been broken, I don't know whether it's better to reset the MiMa versions to whatever passes and have the safety net from this point forward, or to release a 2.0.0 and let tooling flag that some 1.x versions contain breaking changes. The breakage is not a problem for applications using redis4cats directly, but is an issue for libraries that wrap it (e.g., epimetheus-redis4cats).

[rossabaker]

Okay, if we want to proceed checking against compatible versions of each module, I think d61740d will do it. If we want to just start over as 2.0.0, we can drop d61740d, but still want 43e23a2 so the check runs on the new version.