[BUG] Avoid creating unnecessary thread pools on non-remote store node

[Bukhtawar]

Describe the bug

Noticed this thread stack on a non-remote store node. Each thread has a cost(memory) associated with it

"opensearch[9a03514d5df099aadc9e4bef14225c16][low_transfer_queue_consumer][T#3]" #85 daemon prio=5 os_prio=0 cpu=0.10ms elapsed=2140342.61s tid=0x0000fffe82d70de0 nid=0x556d waiting on condition  [0x0000fffe66003000]
   java.lang.Thread.State: WAITING (parking)
        at jdk.internal.misc.Unsafe.park(java.base@17.0.9/Native Method)
        - parking to wait for  <0x0000001009156530> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
        at java.util.concurrent.locks.LockSupport.park(java.base@17.0.9/LockSupport.java:341)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(java.base@17.0.9/AbstractQueuedSynchronizer.java:506)
        at java.util.concurrent.ForkJoinPool.unmanagedBlock(java.base@17.0.9/ForkJoinPool.java:3465)
        at java.util.concurrent.ForkJoinPool.managedBlock(java.base@17.0.9/ForkJoinPool.java:3436)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@17.0.9/AbstractQueuedSynchronizer.java:1625)
        at org.opensearch.repositories.s3.async.SizeBasedBlockingQ$Consumer.consume(SizeBasedBlockingQ.java:180)
        at org.opensearch.repositories.s3.async.SizeBasedBlockingQ$Consumer.run(SizeBasedBlockingQ.java:161)
        at java.util.concurrent.Executors$RunnableAdapter.call(java.base@17.0.9/Executors.java:539)
        at java.util.concurrent.FutureTask.run(java.base@17.0.9/FutureTask.java:264)
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:863)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.9/ThreadPoolExecutor.java:1136)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.9/ThreadPoolExecutor.java:635)
        at java.lang.Thread.run(java.base@17.0.9/Thread.java:840)

Related component

Storage:Performance

To Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Avoid creating unused threadpools

Additional Details

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[mgodwan]

+1, The consumer threads also show up as active in the _cat/thread_pool output as well which can cause confusion although thread is in WAITING state usually.