Attributes to identify services that are using remote sampling

Is your feature request related to a problem? Please describe.
Currently there is no clear way for the collector to identify all the services that are using remote sampling policy - based on Jaeger remote sampling. So if we have to implement an adaptive sampling policy generation at the tracing back-end, one has to monitor root span traffic pattern for all services & root operations and generate the sampling policy for all services. When there is huge number of services & root operations this can be a problematic

Describe the solution you'd like
Enhance the JaegerRemoteSampler class to add attributes to indicate that the service is leveraging remote sampling and also add additional attributes like the sampler type & param. In Jaeger this was achieved since the Probabilistic sampler used to add sampler.type & sampler.param attribute/tag - which is missing in all the samplers provided in the SDK.
Additionally, can we consider adding sampler.type & sampler.param for all the samplers available in the SD?. Currently I believe only RateLimitingSampler (from jaeger-remote-sampler sdk-extenstion) does that.

Start by locating JaegerRemoteSampler and the sampler implementations, then compare their behavior with RateLimitingSampler, which the issue identifies as the existing example. Clarify the attribute names and coverage for remote sampling, sampler type, and sampler parameter before defining completion and validation.