The NO_PROXY parameter does not work in Red Hat Developer Hub

Issue

OpenShift clusters are behind a corporate firewall and can't directly reach out to the Internet. In order to allow some plugins to reach out of the network the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables has been set to use the Internet Proxies in the Backstage CRD and to keep all the internal calls functional. However the plugins that needed to reach out to the Internet worked fine, but all the calls internally started failing with 504 Gateway timeouts because they are not able to reach their destination since they were using the Internet proxies as well.

Following there is the NO_PROXY parameter used in this configuration:

NO_PROXY='.cluster.local,.svc,10.3.131.0/24,10.56.0.0/14,127.0.0.1,172.29.0.0/16,api-int.ocp-hdc-sandbox-ext-1.paas.example.com,is.example.com,localhost,example.com,172.29.0.1,code.example.com'

When the Backstage Plugins tries to request the "https://code.example.com/...", it goes through the proxy and does not respect the NO_PROXY parameter. Backstage Plugins appear to be able to use the HTTP_PROXY and HTTPS_PROXY ok, but do not seem to be working with NO_PROXY.