Redis: Adding the ability to disable adding Events to Activities

[stebet]

Changes

Adds an option for OpenTelemetry.Instrumentation.StackExchangeRedis to disable adding the Redis command lifetime ActivityEvents to Activities. Added this because for example in Honeycomb, Span Events are billed and measured just like individual spans, so Activity Events can quickly gobble up telemetry budgets.

• Appropriate CHANGELOG.md updated for non-trivial changes
• Design discussion issue #

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: stebet / name: Stefán Jökull Sigurðarson (d141ec2, 2813a31)

[stebet]

Another option might be to convert these Events into Tags instead, in case users do not want a separate event for these but would still like the info to be part of the span.

[codecov]

Codecov Report

Merging #416 (bd077fe) into main (76f0b06) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main    #416   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files        163     163           
  Lines       4907    4909    +2     
=====================================
- Misses      4907    4909    +2     

Impacted Files	Coverage Δ
...mentation/RedisProfilerEntryToActivityConverter.cs	0.00% <0.00%> (ø)
...s/StackExchangeRedisCallsInstrumentationOptions.cs	0.00% <0.00%> (ø)

[ejsmith]

This is exactly what I was about to create a PR for. Thank you @stebet! In my case, I'm using Elasticsearch APM and it is converting these activity events into log messages and flooding my app logs with literally millions and millions of useless log messages:

[ejsmith]

It would be super appreciated if we could get this PR merged and a new nuget package pushed out because this behavior is killing my ES APM logs.

[cijothomas]

we can merge once CI is green. @stebet could you fix the markdownlint issues?

[ejsmith]

Awesome! Can we get a new release pushed out? Also, while we are at it, can we do a new release for the Elasticsearch package as well?