using NO_PROXY env variable

### Expected Behaviour

i would like to use NO_PROXY=ip,ip,ip,dns as env variable to not use http_proxy/https_proxy for certain dns/ip.

But in my case the NO_PROXY is not used and the cli just use the http/https proxy set.

### Actual Behaviour

If i export NO_PROXY=adobeioruntime.net, and then run aio rt actions list i get :

```
Datetime Access Kind Version Actions
─────────────── ──────── ──────── ──────── ─────────────────────────────────────────────────
```
where without proxy i have informations in the tab.

### Reproduce Scenario (including but not limited to)

#### Steps to Reproduce

#### Platform and Version
aio info
```
› Warning: @adobe/aio-cli update available from 9.3.0 to 10.0.0.
› Run npm install -g @adobe/aio-cli to update.

System:
OS: Linux 3.10 Red Hat Enterprise Linux 8.7 (Ootpa)
CPU: (4) x64 Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
Memory: 2.35 GB / 23.39 GB
Shell: 4.4.20 - /bin/bash
Binaries:
Node: 14.18.3 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.11 - /usr/local/bin/npm
Virtualization:
Docker: Not Found
npmGlobalPackages:
@adobe/aio-cli: 9.3.0

Proxies:
http: proxy:80
https: proxy:80 (scheme mismatch)
CLI plugins:
core:
@adobe/aio-cli 9.3.0
@adobe/aio-cli-plugin-app 10.7.2
@adobe/aio-cli-plugin-app-templates 1.5.2
@adobe/aio-cli-plugin-auth 3.2.1
@adobe/aio-cli-plugin-certificate 1.0.1
@adobe/aio-cli-plugin-config 4.0.1
@adobe/aio-cli-plugin-console 4.1.0
@adobe/aio-cli-plugin-events 3.3.1
@adobe/aio-cli-plugin-info 3.0.1
@adobe/aio-cli-plugin-runtime 6.2.0
@adobe/aio-cli-plugin-telemetry 1.2.0
@oclif/plugin-autocomplete 1.4.6
@oclif/plugin-help 5.2.20
@oclif/plugin-not-found 2.4.3
@oclif/plugin-plugins 2.4.7
@oclif/plugin-warn-if-update-available 2.1.1
user:
link:
```

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Start by reproducing `aio rt actions list` with `http_proxy`/`https_proxy` set, first with `NO_PROXY=adobeioruntime.net` and then with the proxies unset. Trace the CLI's proxy and environment-variable handling to determine why the request still uses the proxy; done means the command returns the same actions through the configured `NO_PROXY` bypass.

Written by the indexing model from the issue text.