Make Zipkin trace format ready, and remove Zipkin trace analysis and Jaeger format permanently.

[wu-sheng]

According to recent progress around the Service Mesh ecosystem and OpenTelemetry/Prometheus ecosystem, we could be confident to say, we could support metrics w/o requiring trace analysis in some cases.
And back to many discussion in the past several years, there is no chance to support Zipkin trace analysis in a perfect way. So I am going to propose this

1. Make the Zipkin trace ready for ElasticSearch 7
2. Remove all analysis codes, and related libraries.
3. Considering OpenTelemetry collector could have zipkin trace exporter, we don't have to keep the Jaeger receiver and storage plugins anymore. So remove them.

FYI @apache/skywalking-committers , if any of you want to do this, please let me know.