api client ignores HTTPS_PROXY/HTTP_PROXY and NO_PROXY env settings

[neurostream]

for our MCP servers needing external Internet access, we're setting HTTPS_PROXY/HTTP_PROXY/NO_PROXY env vars (passing these as "-e" params for our docker-based tools)

perhaps is this capability for the mcp-server packaging of the brave-search api client already in place, but configured a different way?

[jonathansampson]

Thank you, @neurostream. As noted on the PR, I will take a look at this soon. We very much appreciate the PR :)