chore(deps): update opentelemetry collector and adapt tests

[pichlermarc]

Summary

• All changes from chore(deps): update opentelemetry collector - autoclosed #154
• Adapted tests:
  • transformprocessor's extract_count_metric() now uses the default unit ('1') instead of using the unit from the original histogram. This decision was made as the original histogram unit does never apply to a histogram's count field. For additional info see, see [processor/transform] unit is copied to count metric when using extract_count_metric() open-telemetry/opentelemetry-collector-contrib#31575
  • adapt smoke tests to treat componentMetadata.Name as component.Type, see changes from [component] Change component.Type underlying type to a struct open-telemetry/opentelemetry-collector#9472

Blockers

• Tests are currently failing due to Components subcommand no longer outputs component names open-telemetry/opentelemetry-collector#9855
  • User Impact: dynatrace-otel-collector components would result in wrong output.
  • Can be fixed by applying the upstream fix via a replace directive, see 6cf0f65
• We'd be affected by validate subcommand does not display component names on validation failure open-telemetry/opentelemetry-collector#9863
  • User Impact: dynatrace-otel-collector validate --config=my-config.yaml would validate correctly, but there would not be any suggestions which components are available if validation fails.
  • Can be fixed by applying the upstream fix via a replace directive, see 895b9f2

Additional Information

Replaces #154

[pichlermarc]

Converting back to draft (see blockers in PR body).

[dyladan]

Converting back to draft (see blockers in PR body).

I see you used the replace directive to fix the upstream components. Is this still draft or do we want to review/merge it?

[pichlermarc]

Converting back to draft (see blockers in PR body).

I see you used the replace directive to fix the upstream components. Is this still draft or do we want to review/merge it?

This is still a draft. We discussed offline that we will

• not go ahead with updating to 0.97.0 for now due to the known issues from the blockers section
• not apply the unreleased fixes from upstream at this time

[pichlermarc]

Closing this PR, I'll re-open a new one for the current release.