Add isolate module

[pellared]

Blocked by:

• Log record mutations are visible in next registered processors opentelemetry-specification#4067

Fixes #5823

Benchmark results:

goos: linux
goarch: amd64
pkg: go.opentelemetry.io/contrib/processors/isolate
cpu: Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
BenchmarkLogProcessor/Record_without_shared_data-16         	17212789	        75.12 ns/op	       0 B/op	       0 allocs/op
BenchmarkLogProcessor/Record_with_shared_data-16            	 4411912	       263.3 ns/op	     416 B/op	       2 allocs/op

[codecov]

Codecov Report

Attention: Patch coverage is 57.14286% with 6 lines in your changes missing coverage. Please review.

Project coverage is 64.6%. Comparing base (a952931) to head (648e4fa).

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #5861     +/-   ##
=======================================
- Coverage   64.6%   64.6%   -0.1%     
=======================================
  Files        201     202      +1     
  Lines      12587   12601     +14     
=======================================
+ Hits        8134    8142      +8     
- Misses      4216    4221      +5     
- Partials     237     238      +1     

Files	Coverage Δ
processors/isolate/processor.go	57.1% <57.1%> (ø)

[pellared]

Here is another usage of an no-op processor in a processor implementation.
I think we can think about adding it the the SDK.

See also: #5817 (comment)

EDIT: I created open-telemetry/opentelemetry-go#5580

[MrAlias]

It's not clear to me this is needed currently. We still do not comply with specification regarding our log record type begin passed to the log processor: open-telemetry/opentelemetry-go#5219. The resolution of that may make this type of log processor redundant and unneeded.

I would prefer we resolve prior to adding this kind of extension.

[pellared]

It's not clear to me this is needed currently. We still do not comply with specification regarding our log record type begin passed to the log processor: open-telemetry/opentelemetry-go#5219. The resolution of that may make this type of log processor redundant and unneeded.

I would prefer we resolve prior to adding this kind of extension.

Even if the processor would to accept a fully mutable record - this processor would still be helpful. However, we can postpone this if this is your preference, then please move it to "blocked".

[MrAlias]

Even if the processor would to accept a fully mutable record - this processor would still be helpful. However, we can postpone this if this is your preference, then please move it to "blocked".

With our changes and this still pending, I would prefer to not add this as it has a good potential to be cruft.

moved back to draft