Helix-rest stoppable check endpoint memory leak

[MarkGaox]

Describe the bug

• The helix-rest stoppable check endpoint encounters a memory leak when the server receives a 302 status code and redirects the request three times. Following these redirects, the server hangs after calling _httpClient.execute(postRequest), resulting in the following error:

org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection from pool:
    at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.leaseConnection(PoolingHttpClientConnectionManager.java:316)
    at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$1.get(PoolingHttpClientConnectionManager.java:282)

To Reproduce

• Send the same MZ stoppable check endpoint and receive 3 302 redirect.

Expected behavior

• Should not receive the memory leak error.

Additional context

N/A