Inject proxy configuration in CloudAccount.tm attribute

[AlexanderAtIBM]

Fixes #2344

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ AlexanderAtIBM
❌ Alexander Lodolo

---

Alexander Lodolo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Siddharthgolecha]

Hi @AlexanderAtIBM , as I mentioned in my email, one of the client also applied your patch and this is what they say

The proxy parameters passed to QiskitRuntimeService aren’t making it all the way down to the requests layer, and the same happens with verify=False.

As a workaround, he:

1. Defined the proxy via http_proxy and https_proxy environment variables.
2. Manually force verify=False inside requests/api.py around line 55.

kwargs["verify"] = False
with sessions.Session() as session:
    return session.request(method=method, url=url, **kwargs)

Example workaround:

os.environ["http_proxy"] = f"http://{username_ntlm}:{password_ntlm}@{proxy_address}"
os.environ["https_proxy"] = f"http://{username_ntlm}:{password_ntlm}@{proxy_address}"
service = QiskitRuntimeService(..., verify=False)

These settings aren’t being forwarded through the intermediate layers. So, I would request you to include these in your patch.

[AlexanderAtIBM]

Hi @Siddharthgolecha,
I added the ssl_verification argument injection in the CloudAuth class.