GH-1258: Change OOMHandler to JavaLangErrorHandler

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

Call the handler for all `Error`s on container threads.

**I will do the cherry-pick; there will be conflicts**

src/reference/asciidoc/amqp.adoc

@@ -5685,6 +5685,15 @@ a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]
 
+|javaLangErrorHandler
+(N/A)
+
+|An `AbstractMessageListenerContainer.JavaLangErrorHandler` implementation that is called when a container thread catches an `Error`.
+The default implementation calls `System.exit(99)`; to revert to the previous behavior (do nothing), add a no-op handler.
+
+a|image::images/tickmark.png[]
+a|image::images/tickmark.png[]
+
 |maxConcurrentConsumers
 (max-concurrency)
 
@@ -5789,15 +5798,6 @@ a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]
 a|image::images/tickmark.png[]
 
-|oOMHandler
-(N/A)
-
-|An `AbstractMessageListenerContainer.OOMHandler` implementation that is called when a container thread catches an `OutOfMemoryException`.
-The default implementation calls `System.exit(99)`.
-
-a|image::images/tickmark.png[]
-a|image::images/tickmark.png[]
-
 |phase
 (phase)
 

src/reference/asciidoc/whats-new.adoc

@@ -38,7 +38,8 @@ See <<template-confirms>> for more information.
 
 A new listener container property `consumeDelay` is now available; it is helpful when using the https://github.com/rabbitmq/rabbitmq-sharding[RabbitMQ Sharding Plugin].
 
-The default `OOMHandler` (out of memory handler) now calls `System.exit(99)`.
+The default `JavaLangErrorHandler` now calls `System.exit(99)`.
+To revert to the previous behavior (do nothing), add a no-op handler.
 
 See <<containerAttributes>> for more information.