Remove unit test due to threading limitations with Mockito

This commit removes a unit test that relied on Mockito to mock static methods inside a separate thread. Mockito encounters issues when mocks are accessed across different threads, leading to inconsistent behavior and null values in asynchronous contexts.

The test was causing failures due to these limitations, as static mocks were not reliably available within the ExecutorService thread. A potential solution could involve restructuring the code to allow synchronous execution in a single-threaded context for testing purposes, or exploring alternative approaches for mocking in multi-threaded scenarios.

Further investigation into better testing strategies for this case is recommended.

Author: Aaron Echavarria