bpfman-operator/agent and Egress Proxy Support

In clusters using an egress proxy, it is crucial to ensure that bpfman-operator and bpfman-agent respect the http_proxy and no_proxy environment variables. This will determine whether these components can successfully communicate through the proxy.

At https://curl.haxx.se/docs/manual.html there's description of environment variables related to using HTTP proxy which libcurl/curl understands:

> ENVIRONMENT VARIABLES
>
> Curl reads and understands the following environment variables:
http_proxy, HTTPS_PROXY, FTP_PROXY
>
> They should be set for protocol-specific proxies. General proxy should be set with
ALL_PROXY
>
> A comma-separated list of host names that shouldn't go through any proxy is set in (only an asterisk, '*' matches all hosts)
NO_PROXY
>
> If the host name matches one of these strings, or the host is within the domain of one of these strings, transactions with that node will not be proxied.
>
> Please notice that http_proxy is spelled lowercase as the only one among these variables. Some libraries/programs look for lowercase names of these variables whereas others look for upppercase names. To be safe one should define both lowercase and uppercase versions of each variable.

Start by locating the bpfman-operator and bpfman-agent entry points and how their cluster communication is configured. Check the curl documentation linked in the issue for proxy environment-variable behavior. Done means both components respect http_proxy and no_proxy when communicating through an egress proxy.

Written by the indexing model from the issue text.