build(deps): bump newrelic_rpm from 10.5.0 to 10.6.0

[dependabot]

Bumps newrelic_rpm from 10.5.0 to 10.6.0.

Changelog

Sourced from newrelic_rpm's changelog.

v10.6.0

• Feature: SpanLink events are now supported for the Hybrid Agent

Spans created by an OpenTelemetry API can now have Span Links associated with them. Links can be added on a span's start, by passing them to the links argument, or by calling the OpenTelemetry::Trace::Span#add_link API. PR#3586

• Feature: SpanEvent events are now supported for the Hybrid Agent

Spans created by an OpenTelemetry API can now have SpanEvent events associated with them via the OpenTelemetry::Trace::Span#add_event API. SpanEvent events capture timestamped annotations on a span and are sent to New Relic alongside the parent span. PR#3587

• Feature: Set Span Kind on all Hybrid Agent spans

  Previously, only OpenTelemetry spans translated into external request segments or datastore segments added span kind as an attribute. Now, the agent adds span kind to all OpenTelemetry spans where the value is available. PR#3589

• Feature: Add support for OpenTelemetry::Tracer#start_root_span

  The OpenTelemetry::Tracer#start_root_span API can now be used to force a transaction to start for a given span, provided it has a :server or :consumer span kind. For any other span kinds, it will no-op. This method is most commonly used in background job instrumentation. PR#3588

• Bugfix: Fix instrumentation.rails_event_logger: false not disabling the instrumentation

  Setting instrumentation.rails_event_logger to false was not disabling the Rails.event instrumentation as expected. The instrumentation would still be installed during Rails boot. This has been fixed. PR#3564

• Bugfix: Normalize boolean-like values to disabled for instrumentation config keys

  Setting any instrumentation.* config key to false, no, or off instead of disabled will now resolve to disabled and prevent the instrumentation from being installed. PR#3579

• Bugfix: Per-library logging supportability metrics now reflect each library's instrumentation state

  The Supportability/Logging/Ruby/{library}/{enabled|disabled} metrics previously echoed application_logging.enabled for every library, so disabling a single logging instrumentation or running without one of its gems still reported enabled. Each library now reports based on its own instrumentation state. PR#3571

Commits

• b642757 Merge pull request #3596 from newrelic/prerelease_updates_10.6.0-pre
• 3a7a9a4 Fix order of entries
• 555e859 Apply suggestion from @​kaylareopelle
• 46e2690 bump version
• 776d99f Merge pull request #3595 from newrelic/release-success-triggers
• 7f4ee6f Gate Lambda Release by successful release workflow
• 3b04866 Merge pull request #3591 from newrelic/translate_messaging_attrs
• db9c26c rubocop
• 0f8a901 Update root span test
• a8bd5fd Merge pull request #3594 from newrelic/if_31_pin_i18n
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)