feat(tracing-apps): Bump otel collector

[isantospardo]

Description

Related to #1603

Bump opentelemetryCollector from 0.135.0 to 0.142.1

Issues

logging exporter deprecated to debug

exporters:
  debug: {}

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated the changelog with an artifacthub.io/changes annotation in Chart.yaml, check the example in the documentation.
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released

[hairmare]

Why not use this one from tracing-apps:

helm-charts/charts/tracing-apps/values.yaml

Lines 21 to 39 in d3edfb9

	# -- [opentelemetry-collector](https://opentelemetry.io/docs/collector/) ([example](./examples/opentelemetryCollector.yaml))
	# @default -- -
	opentelemetryCollector:
	# -- Enable otel-exporter
	enabled: false
	name: otel-collector
	destination:
	# -- Namespace
	namespace: "infra-otel-operator"
	# -- Repo URL
	# @default -- [repo](https://open-telemetry.github.io/opentelemetry-helm-charts)
	repoURL: "https://open-telemetry.github.io/opentelemetry-helm-charts"
	# -- Chart
	chart: "opentelemetry-collector"
	# -- [opentelemetry-collector Helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector)
	targetRevision: "0.135.0"
	# -- Helm values
	# @default -- [upstream values](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/values.yaml)
	values: {}

[isantospardo]

Why not use this one from tracing-apps:

helm-charts/charts/tracing-apps/values.yaml

Lines 21 to 39 in d3edfb9

	# -- [opentelemetry-collector](https://opentelemetry.io/docs/collector/) ([example](./examples/opentelemetryCollector.yaml))
	# @default -- -
	opentelemetryCollector:
	# -- Enable otel-exporter
	enabled: false
	name: otel-collector
	destination:
	# -- Namespace
	namespace: "infra-otel-operator"
	# -- Repo URL
	# @default -- [repo](https://open-telemetry.github.io/opentelemetry-helm-charts)
	repoURL: "https://open-telemetry.github.io/opentelemetry-helm-charts"
	# -- Chart
	chart: "opentelemetry-collector"
	# -- [opentelemetry-collector Helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector)
	targetRevision: "0.135.0"
	# -- Helm values
	# @default -- [upstream values](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/values.yaml)
	values: {}

Just to differentiate between traces and logs, what do you think?

[hairmare]

Just to differentiate between traces and logs, what do you think?

I think we should mainly install one otel-collector per cluster and that there shoul donly be one upstream path for that. In the big picture logs are just traces with less metadata.