Fix memory leak on read error

[Exca-DK]

Description

This PR fixes a potential memory leak that occurs when a read error happens while processing the response body.

According to the net/http package documentation:

The caller must close the response body when finished with it.

Failing to close the response body on read errors can lead to resource leaks. This change ensures proper cleanup in such cases.

Test Plan

Testing this issue is not straightforward, as it depends on network failures. The read operation may return an error, as seen in the Go source reference.

One way to simulate this in a controlled environment is by setting an invalid Content-Length in the response header on the server side, forcing a read error:

handler := func(w http.ResponseWriter, r *http.Request) {
    w.Header().Set("Content-Length", "1")
}

This should trigger an unexpected EOF error when reading the response body.

Related Links

None.

[gregnazario]

lgtm, please update the changelog