GH-1318: Support the Global Flag in basicQos

Resolves https://github.com/spring-projects/spring-amqp/issues/1318

**cherry-pick to 2.2.x**

src/reference/asciidoc/amqp.adoc

@@ -5672,6 +5672,15 @@ You can set it to `false` to revert to the previous behavior.
 a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]
 
+|globalQos
+(global-qos)
+
+|When true, the `prefetchCount` is applied globally to the channel rather than to each consumer on the channel.
+See https://www.rabbitmq.com/amqp-0-9-1-reference.html#basic.qos.global[`basicQos.global`] for more information.
+
+a|image::images/tickmark.png[]
+a|image::images/tickmark.png[]
+
 |(group)
 
 |This is available only when using the namespace.
@@ -5866,6 +5875,7 @@ to a large amount of memory in the client process), and if strict message orderi
 (the prefetch value should be set back to 1 in this case).
 Also, with low-volume messaging and multiple consumers (including concurrency within a single listener container instance), you may wish to reduce the prefetch to get a more even distribution of messages across consumers.
 
+Also see `globalQos`.
 
 a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]

src/reference/asciidoc/whats-new.adoc

@@ -41,6 +41,8 @@ A new listener container property `consumeDelay` is now available; it is helpful
 The default `JavaLangErrorHandler` now calls `System.exit(99)`.
 To revert to the previous behavior (do nothing), add a no-op handler.
 
+The containers now support the `globalQos` property to apply the `prefetchCount` globally for the channel rather than for each consumer on the channel.
+
 See <<containerAttributes>> for more information.
 
 ==== MessagePostProcessor Changes