Support mTLS for JaegerRemoteSampler when instantiated via JaegerRemoteSamplerProvider in autoinstrumentation

Is your feature request related to a problem? Please describe.

I'd like to allow autoinstrumented Java code that elects to use otel.traces.sampler=jaeger_remote to be able to pass mTLS specific information to JaegerRemoteSamplerProvider. Currently there is no way to enable mTLS via the otel.traces.sampler.arg configuration parameter, as it supports only

• endpoint
• polling interval
• initialSamplingRate

Describe the solution you'd like

Support for JaegerRemoteSampler mTLS communication via the otel.traces.sampler* configuration variables.

Describe alternatives you've considered

Write Otel-specific code in every Java application that wants to be auto-instrumented to call JaegerRemoteSamplerBuilder.set{ClientTls,TrustedCertificates} and somehow (likely via a custom Javaagent extension) override the sampler construction at SDK initialization time.

Start with JaegerRemoteSamplerProvider.java and trace how otel.traces.sampler and otel.traces.sampler.arg are parsed and passed to the sampler. Review JaegerRemoteSamplerBuilder.setClientTls and setTrustedCertificates to determine how mTLS settings could be represented through those configuration variables. Done means autoinstrumented Java applications can configure Jaeger remote sampling with mTLS without custom sampler construction.