NO_PROXY environment variable ignored if used as dotnet local tool

Description

We have an internal nuget feed on the local LAN but we don't have direct internet connection, we must use the proxy to reach the official nuget.org repository, so we have:

1. HTTP_PROXY/HTTPS_PROXY set to point to the internal proxy
2. NO_PROXY set to the internal nuget host name to bypass the proxy

Downloading packages from nuget.org works fine with both dotnet tool and paket.exe but when it tries to download packages from the internal feed dotnet paket install fails, while paket.exe install works regularly. In the former case requests are issued to the proxy rather than to the nuget host: it looks like the NO_PROXY environment variable gets discarded by the dotnet local tool, at least on windows. I can't tell wether the issue is in paket itself or it is a generalized problem with environment variables on dotnet local tools.

The issue shows at least with paket 7.1.5 and 7.0.x, I can't try with earlier versions because we net .net 6 support.

Known workarounds

The only workaround I'm aware of is to use paket.exe

Reproduce dotnet paket install with HTTP_PROXY, HTTPS_PROXY, and NO_PROXY set, then compare it with paket.exe install. Determine whether the local-tool launch or Paket handling drops NO_PROXY; done means the internal feed bypasses the proxy while nuget.org still uses it, with regression coverage for the behavior.