Support for use of locally generated certificates when hosting Agenta locally in OSS mode

[DBairdME]

Is your feature request related to a problem? Please describe.
When hosting Agenta locally in OSS mode, would like to ensure that any communication between users and Agenta web app, and applications to Agenta backend is via HTTPS. Issue is that in a locally hosted environment, the certificates used are provisioned by internal IT teams, with the Root CA and cert chain being needed to ensure HTTPS connectivity is validated.
Appears that the Agenta CLI and SDK don't allow the injection of the additional CA / cert chain info in the requests (ag.init(), etc.)

• Tests indicate that while an HTTP connection works, the HTTPS based connection fails. Agenta CLI reports an SSL error, and the SDK shows that "Traces will not be exported" when using HTTPS instead of HTTP
  Issue appears to also impact Agenta web to backend communication - some configuration items can be amended but tests / variants cannot be connected to with a httpx.ConnectError thrown for the connection to the test container

Describe the solution you'd like
Is it possible to use locally based certificates with this platform when it's locally based. Ideally, a configuration file should be available to provide the path to the RootCA / cert chain so that this can be used for any connection setup between the frontend and backend, and from clients to the backend
For reference, standard methods to inject the cert information work for standard HTTPS connections, suggesting that Agenta (or OpenTelemetry) is using something else in it's connection setup.

Describe alternatives you've considered
Have considered just having everything as HTTP, but this will likely be an issue with internal IT Sec and Governance policies