JaegerExporter batching changes

[CodeBlanch]

Fixes #1388
Fixes #1730

See:

• Identify dependencies in the UI when remote is not instrumented jaegertracing/jaeger-ui#594
• Identify uninstrumented services jaegertracing/jaeger-ui#659

Changes

Removes the logic we had to generate a process/batch for each service when sending spans to Jaeger.

Impact

Using the new code Jaeger UI v1.12.0 spans will look like this:

Before they looked like this:

What the extra logic was doing was tricking Jaeger UI into treating the non-reporting dependencies as dependencies WRT the UI.

• CHANGELOG.md updated for non-trivial changes

[codecov]

Codecov Report

Merging #1732 (520ae75) into main (d724634) will increase coverage by 0.04%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##             main    #1732      +/-   ##
==========================================
+ Coverage   83.11%   83.16%   +0.04%     
==========================================
  Files         193      193              
  Lines        6005     5986      -19     
==========================================
- Hits         4991     4978      -13     
+ Misses       1014     1008       -6     

Impacted Files	Coverage Δ
...nTelemetry.Exporter.Jaeger/Implementation/Batch.cs	84.09% <ø> (+3.65%)	⬆️
...rc/OpenTelemetry.Exporter.Jaeger/JaegerExporter.cs	83.33% <72.72%> (-1.93%)	⬇️
...emetry.Api/Internal/OpenTelemetryApiEventSource.cs	82.35% <0.00%> (+5.88%)	⬆️
...ZPages/Implementation/ZPagesExporterEventSource.cs	62.50% <0.00%> (+6.25%)	⬆️

[CodeBlanch]

Sorry @ndrwrbgs I know this feature was important to you. Our job in OpenTelemetry .NET is to be compliant with the main OpenTelemetry spec so we have to do this. @cijothomas is going to take up pursuing a change through the official spec channels.