Split remote sampling feature from the Jaeger receiver

[jpkrohling]

As discussed during the latest GC call with @bogdandrutu, it could be beneficial to other components to split the remote sampling proxy from the Jaeger receiver into its own extension.

• Create the initial skeleton #6631
• Add the HTTP server #6632
• Tie in the client config manager proxy #6695
• Add the gRPC server #6694
• Remove remote sampling endpoint from the Jaeger receiver #6633

[jpkrohling]

@frzifus, is there anything else pending on this?

[frzifus]

I don't really think so. Just removing the components from the receiver in release v0.61.

Maybe registering the extention as a component? Is there a document that describes what exactly has to be done for this #13005 (comment)

[jpkrohling]

Just this: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components

But it's missing the step to add the component to the manifests in the releases repository: https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-contrib/manifest.yaml

Would you be open to sending a PR enhancing the contribution guidelines, and adding this last step?

[frzifus]

sure, do i need to create an issue first or should i link it to this one?

[jpkrohling]

Your choice. There's no need to have a dedicated issue for that, although I like to do it as it helps me keep track of my activities.

[frzifus]

i think we can close that one too.
cc @jpkrohling