[BUG] LogsIngestionClient does not use its ThreadPool for processing

[FelixStumvollDT]

Describe the bug
I was looking at the source code of the LogsIngestionClient, since i was wondering why it implements the AutoClosable interface.
I noticed it creates an ExecutorService instances, that has to be shut down. However, upon closer inspection i saw that this ExecutorService is not used for any processing. Only here are tasks submitted to it, and the passed tasks immediately returns the Stream instance, which is essentially a no-op.

Code Snippet
The relevant code is in the submit method of the LogsIngestionClient:

private Stream<UploadLogsResponseHolder> submit(Stream<UploadLogsResponseHolder> responseStream, int concurrency) {
    if (concurrency == 1) {
        return responseStream;
    }

    try {
        return threadPool.submit(() -> responseStream).get();
    } catch (InterruptedException | ExecutionException e) {
        throw LOGGER.logExceptionAsError(new RuntimeException(e));
    }
}

Setup (please complete the following information):

• OS: -
• IDE: -
• Library/Libraries: com.azure:azure-monitor-ingestion:1.2.2
• Java version: 21
• App Server/Environment: -
• Frameworks: -

[github-actions]

@anuchandy @conniey @lmolkova

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.