- Add a new method Publisher.NotifyPublishWithReturn that ensures proper pairing
  of returns and confirmations according to RabbitMQ protocol where returns are
  immediately followed by confirmations for unroutable messages
- Add comprehensive integration tests covering routable/unroutable scenarios
  with mandatory and non-mandatory publishing

This addresses the issue where NotifyPublish() and NotifyReturn() handlers
run in separate goroutines and can go out of order, making it difficult to
properly link returned messages with their confirmations for reliable
unrouted message handling.

feat: add queue message expiration option for consumer

fix: Use rabbitmq:4.1.1-alpine in integration test

Feature: Added connection state check

Fix: Redact password from URL

chore: initial integration test

Signed-off-by: Ben Meier <ben.meier@humanitec.com>

fix: pass shuffle param to StaticResolver

bugfix: graceful consumer shutdown

fix: initialise handlerMu in consumer (#169)

Rename mux->mu and update amqp

Add cluster support via Resolver

Consumer: close gracefully

fix: consumer close before run

Signed-off-by: Ruslan Bayandinov <wazsone@ya.ru>

update `amqp091-go` from `v1.7.0` to `v1.9.0`

docs and multiple exchanges

Return an error instead of crashing when we cannot retry consumer

Remove tracef from logger interface

fix: fatal default log