Rationalize thread pool executor usage

4 thread pools:
 - executor service for internal tasks (e.g. run connection recovery)
 - scheduled executor service for internal scheduled tasks (e.g.
   schedule a connection retry)
 - publisher executor service to poll settlement futures
 - consumer executor service to poll receivers

 The tasks to run are different in nature, it explains the different
 executor services to configure. The library uses sensible defaults (e.g
 virtual threads if available for the publisher executor service, where
 there is a short task for each message; platform threads for the
 consumer executor, where tasks are long-running).

 Virtual threads do not seem appropriate for long-running tasks,
 especially when testing against cluster rolling restart.

Author: rabbitmq-ci

0.1.0-SNAPSHOT/htmlsingle/index.html

@@ -655,7 +655,7 @@
 <h1>RabbitMQ AMQP 1.0 Java Client</h1>
 <div class="details">
 <span id="revnumber">version 0.1.0-SNAPSHOT</span>
-<br><span id="revremark">(94e0f5b)</span>
+<br><span id="revremark">(dfbeab2)</span>
 </div>
 <div id="toc" class="toc2">
 <div id="toctitle">Table of Contents</div>
@@ -2213,7 +2213,7 @@ <h4 id="observability-metrics-publish-observation"><a class="anchor" href="#obse
 <div id="footer">
 <div id="footer-text">
 Version 0.1.0-SNAPSHOT<br>
-Last updated 2024-09-05 06:53:26 UTC
+Last updated 2024-09-05 09:06:19 UTC
 </div>
 </div>
 </body>

snapshot/htmlsingle/index.html

@@ -655,7 +655,7 @@
 <h1>RabbitMQ AMQP 1.0 Java Client</h1>
 <div class="details">
 <span id="revnumber">version 0.1.0-SNAPSHOT</span>
-<br><span id="revremark">(94e0f5b)</span>
+<br><span id="revremark">(dfbeab2)</span>
 </div>
 <div id="toc" class="toc2">
 <div id="toctitle">Table of Contents</div>
@@ -2213,7 +2213,7 @@ <h4 id="observability-metrics-publish-observation"><a class="anchor" href="#obse
 <div id="footer">
 <div id="footer-text">
 Version 0.1.0-SNAPSHOT<br>
-Last updated 2024-09-05 06:53:26 UTC
+Last updated 2024-09-05 09:06:19 UTC
 </div>
 </div>
 </body>