[FDS-2525] Authenticated export of telemetry data

[BryanFauble]

Problem:

1. When creating telemetry data where an open-telemetry collector is not available to perform an oauth2 token exchange the only way to attach an auth token on outbound requests was to define a static header an environment variables.

Solution:

1. Adding the requests-oauth2client library that will handle the oauth2 token exchange with Auth0 for us if the environment variables are set.
2. Attach the auth mechanism on the requests.Session() object that the opentelemetry exporter uses to send data out.
3. This is the first portion of https://sagebionetworks.jira.com/browse/FDS-2525 - Which allows developers to export telemetry data locally. It also verifies that all we need to do for FDS-2525 is set a few environment variables and allow schematic running within AWS to export it's data to the OTEL collector, which will then forward the data to the DPE K8s cluster.

Testing:

1. I ran this code locally with the environment variables set and confirmed that both traces AND log were exported and viewable within SigNoz on the sandbox kubernetes cluster.
2. I also verified I could point this at the https://dev.sagedpe.org URL too

TODO:

• Remove hacky code around verify=False for the HTTP POST logic when non-self signed certs can be used.

[thomasyu888]

🔥 LGTM! Thanks for doing this. Make sense to me, I'll leave it to at least one other developer to review this.

[GiaJordan]

@BryanFauble The changes look good to me!
I just see that a couple tests are failing and there are a couple merge conflicts.

[sonarcloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
45.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud