Port of jaeger remote sampler

[sconover]

Depends on proposed changes to opentelementry python:
open-telemetry/opentelemetry-python#3852

Description

This is an early PR that proposes to add jaeger remote sampling support to the contrib repo.
Given that this is a port, there are multiple issues to discuss, from code style to overall approach to
properly integrating these samplers into the opentelemetry-python trace client lib.

Once all TODO's are resolved, in this PR and the PR it depends on, docs need to be added/updated.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Ported unit tests from jaeger-client-python
• For lack of end-to-end tests, I put together a sample flask app and, running alongside a jaeger agent, manually verified that remote configuration changes indeed sync over to the client and change the client's sampling decision behavior.

Does This PR Require a Core Repo Change?

• Yes. - Link to PR: Support for Jaeger Remote Sampling addition to contrib repo opentelemetry-python#3852

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project (I believe so)
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[aabmass]

I hate to go back and forth on this, but shouldn't this be in the core repo @srikanthccv? It's a part of the official OTel SDK spec now https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#jaegerremotesampler.

[srikanthccv]

I forgot that it was part of the official spec. I had seen go implementation in their contrib repo https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/samplers/jaegerremote. I apologize for the back and forth. The original PR in the core repo implemented it in the SDK package itself. It can be part of the core repo but I think it should be a separate package (similar to jaeger propagator).

[aabmass]

It can be part of the core repo but I think it should be a separate package (similar to jaeger propagator).

👍 that sounds good to me. @sconover apologies for the miscommunication