* Add `throws Exception` to the `ProtonDeliveryListener.onDelivery()`
contract to avoid any possible misleading transformations in the implementation
* Add `AcknowledgingProtonDeliveryListener` contract as an extension of the
`ProtonDeliveryListener`.
Enforce its logic to a new contract with an `AmqpAcknowledgment` argument
populated by the `AmqpMessageListenerContainer`.
Such a contract is necessary to properly delegate replenish link credits logic back
to the listener container.
This logic is now included in the `AmqpMessageListenerContainer.doInvokeListener()` method.
Either way, the target implementation is till free to deal with `Delivery` whatever is possible.
However, there is a possibility of inconsistency when the container is paused, but
listener calls `addCredit()` on the delivery's receiver
* Add `HandlerAdapter.getMethod()` to avoid extra method parameter propagation to consumers of
the `HandlerAdapter`
* Extract `record ReplyExpressionRoot` from the `AbstractAdaptableMessageListener`
to make it available for any other not RabbitMQ-based modules
* Implement `AmqpMessagingListenerAdapter` for AMQP 1.0 client.
It is similar to the `MessagingMessageListenerAdapter` for RabbitMQ-based modules,
and is going to be used for POJO-based event-driven message handling, e.g. future `@AmqpListener`.
A lot of `AmqpMessagingListenerAdapter` logic is really a copy/paste
from the `MessagingMessageListenerAdapter` and its super class

* Fix typos in the `AmqpListenerErrorHandler` & `AmqpMessagingListenerAdapter` Javadocs
* Remove redundant `@Nullable` from `AmqpMessagingListenerAdapter`'s
`setErrorHandler()`, `setMessageConverter()` and `setBeanResolver()`
* Remove `projectionUsed` property logic from the `AmqpMessagingListenerAdapter.invokeHandlerAndProcessResult()`
as it looks like that message property is out of use anywhere in the project