Stack traces are not informative when using HttpConnection

[JoshMock]

🐛 Bug Report

When the client is configured to use HttpConnection instead of the default UndiciConnection class, error stack traces are often too brief:

ConnectionError: socket hang up - Local: 127.0.0.1:61564, Remote: 127.0.0.1:9200
    at KibanaTransport.request (/Users/afharo/Developer/elastic/kibana/node_modules/@elastic/transport/src/Transport.ts:585:17)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

Likely due to http swallowing the stack during async operations.

See elastic/kibana#60237

Expected behavior

A full stack trace back to the original API call that triggered the error.