Document Direct Reply-To for AMQP (#2358)

* Document Direct Reply-To for AMQP

* Document Direct Reply-To usage for AMQP 1.0 (docs for
  rabbitmq/rabbitmq-server#14474)
* Provide code examples how to use Direct Reply-To for AMQP 1.0 and AMQP
  0.9.1. For now, only an example using the Erlang client is provided.
  Other clients will follow separately.
* Provide a better description when to use and when NOT to use Direct
  Reply-To.

* Add AMQP Java request/response direct reply-to example

* Check requester is still connected in request/response example

---------

Co-authored-by: Arnaud Cogoluègnes <[email protected]>

Author: ansd

docs/amqp.md

@@ -307,7 +307,6 @@ This section lists features that RabbitMQ supports exclusively in AMQP 1.0, whic
 
 ### AMQP 0.9.1 Features
 This section lists features that RabbitMQ supports exclusively in AMQP 0.9.1, which are currently not available in AMQP 1.0:
-* **[Direct Reply-to](./direct-reply-to)**: While AMQP 1.0 clients can perform Remote Procedure Calls (RPCs) by declaring a reply queue (as [described](https://rabbitmq.github.io/rabbitmq-amqp-java-client/stable/htmlsingle/#remote-procedure-call-rpc) in the RabbitMQ AMQP 1.0 Java client), the Direct Reply-to feature is only available in AMQP 0.9.1.
 * **[AMQP 0.9.1 Channel Interceptor](https://github.com/rabbitmq/internals/blob/master/interceptors.md)**: Plugins, such as the [Sharding Plugin](https://github.com/rabbitmq/rabbitmq-server/tree/main/deps/rabbitmq_sharding#rabbitmq-sharding-plugin), that intercept and modify frames are [currently](https://github.com/rabbitmq/rabbitmq-server/issues/10051) only supported for AMQP 0.9.1.
 * **Message rates in the Management UI**: Message rates for exchanges and queues are shown in the Management UI for AMQP 0.9.1 connections. These rates are not available for AMQP 1.0 connections.
 * **[Transactions](./semantics)**: AMQP 0.9.1 provides limited support, whereas AMQP 1.0 currently does not support transactions (as listed in the [limitations](#limitations)).

docs/confirms.md

@@ -81,7 +81,7 @@ so the delivered message can be marked for future deletion.
 Sometimes publishing and consuming applications need to communicate via requests and responses
 that need an explicit acknowledgement from the peer. [RabbitMQ tutorial #6](/tutorials)
 demonstrates the basics of how that's done, and [Direct Reply-to](./direct-reply-to) provides
-a way to do it without declaring a lot of short-lived temporary response queues.
+a way to do it without creating response queues.
 
 This type of communication, however, is not covered in this guide, and is mentioned only to
 contrast it with the much more focussed messaging protocol features described in this guide.