[Bug]: ChromaClient times out on Vercel's Edge network

### What happened?

```
const client = new ChromaClient({
path: process.env.CHROMA_URL,
});
console.log(client.heartbeat())
```

Is timing out on Vercel's Edge network, without sending a request through to the server that's hosting Chroma. I can access the server fine from other projects, or with the same file but not using the edge runtime. But not on the Edge.

There's no error returned, it just hangs.

I'm guessing its something to do with the APIs supported on the Edge by Vercel: https://vercel.com/docs/functions/edge-functions/edge-runtime#supported-apis ??

@moreno1123 reported a similar problem on langchain, but I _think_ it's a chromaclient issue, hence raising here.
https://github.com/langchain-ai/langchainjs/issues/3521

### Versions

ChromaDB 1.6.1

Start by reproducing the ChromaClient heartbeat entry point on Vercel's Edge runtime and compare it with the same code outside Edge. Inspect the request path used by ChromaClient and the APIs supported by the Edge runtime; done means the heartbeat completes or reports a useful error instead of hanging.

Written by the indexing model from the issue text.