`respect` command does not honour `HTTP_PROXY` / `HTTPS_PROXY` environment variables for outbound API requests — unusable in corporate networks

[saismrutiranjan18]

Bug — respect command ignores HTTP_PROXY / HTTPS_PROXY — unusable behind corporate proxies

Problem

The v2.20.5 changelog fixed HTTP_PROXY support for the push command but the same fix was not applied to respect-core's request layer. Teams behind corporate proxies cannot run Respect contract tests — they receive ECONNREFUSED with no proxy-related guidance.

Environment

• Corporate network with HTTPS_PROXY set
• redocly respect api.arazzo.yaml --server https://internal-api.example.com
• Result: ECONNREFUSED — proxy is not used

Expected

All outbound HTTP requests made by respect should honour HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables, consistent with the push command fix in v2.20.5.