- Added EventName(to event_processor) and CommandName(to command_proc…

…essor) (ThreeDotsLabs#548)

Co-authored-by: itbewhatitdo <itbewhatitdo.app@gmail.com>

feat(cqrs): add ability to return handlers for CQRS EventProcessor an…

…d CommandProcessor (ThreeDotsLabs#544)

get rid of github.com/gogo/protobuf (ThreeDotsLabs#526)

added ForceShort for test features (ThreeDotsLabs#537)

fix flaky TestEventProcessor_handler_group (ThreeDotsLabs#534)

Router: publish messages in bulk (ThreeDotsLabs#513)

Currently, the router will publish produced messaged by calling Publish individually, even though the bulk API exists.

This change works the same, although it can be handy for some custom implementations when you want to treat the produced messages as a group. For some implementations, it could also slightly improve publish performance.

Add more docs on requeue (ThreeDotsLabs#509)

Requeuer and Message Delay (ThreeDotsLabs#469)

* Added the `Requeuer` component.
    * It works as a simpler version of the Forwarder, routing messages from one topic to another (a dynamic one).
    * Can be used to move messages that failed to process back to the original topic, so they don't block other messages.
    * Can be used together with the poison middleware and the `delay` component to delay the forwarding. 
* Added the `delay` package. It contains helpers for setting delay metadata on messages.
    * **Does not do anything by itself.** A Pub/Sub needs to support it explicitly. For now, that's the delayed postgres Pub/Sub implemented in  ThreeDotsLabs/watermill-sql#34
    * Use case 1: publishing a message after a given delay or at given time (see the example).
    * Use case 2: automatically moving messages out of the poison queue to the original topic after a delay (used together with the `Requeuer` component).
* Added the `pq` CLI tool for working with poison queues.

docs: Add running the Router

Fix tests running concurrent publish with the same messages (ThreeDot…

…sLabs#479)