Use number of available processors for queue count in test

Instead of 10. This decreases load for low-resource environments,
like CI (usually ~ 4 available processors). The VM has to run the test
suite itself, but also the 3-node cluster.

Author: acogoluegnes

src/test/java/com/rabbitmq/client/amqp/impl/RecoveryClusterTest.java

@@ -78,7 +78,7 @@ public class RecoveryClusterTest {
   @BeforeAll
   static void initAll() {
     nodes = Cli.nodes();
-    LOGGER.info("Available processor(s): {}", Runtime.getRuntime().availableProcessors());
+    LOGGER.info("Available processor(s): {}", Utils.AVAILABLE_PROCESSORS);
   }
 
   @BeforeEach
@@ -127,7 +127,7 @@ void clusterRestart() {
     LOGGER.info("Cluster restart test...");
     LOGGER.info("Available processors: {}", Runtime.getRuntime().availableProcessors());
     LOGGER.info("Java version: {}", System.getProperty("java.version"));
-    int queueCount = 10;
+    int queueCount = Utils.AVAILABLE_PROCESSORS;
     List<Management.QueueType> queueTypes =
         List.of(
             Management.QueueType.STREAM,