Update Tempo's open-telemetry/collector dependency

[yvrhdn]

Is your feature request related to a problem? Please describe.

Tempo depends on go.opentelemetry.io/collector for its receivers. We are currently still using v0.21 while the latest version is already v0.38...

tempo/go.mod

Line 57 in c5d007d

go.opentelemetry.io/collector v0.21.0

The receivers are used by the distributor: https://github.com/grafana/tempo/search?q=go.opentelemetry.io%2Fcollector

Describe the solution you'd like

Update the dependency.
Update the documentation if this changes any defaults (I'm thinking about #637).

Describe alternatives you've considered

If we don't update we are going to miss out on security and performance improvements.

Additional context
N/A

[yvrhdn]

We should probably also look into updating our opentelemetry-proto submodule:

tempo/.gitmodules

Lines 1 to 3 in c5d007d

	[submodule "opentelemetry-proto"]
	path = opentelemetry-proto
	url = https://github.com/open-telemetry/opentelemetry-proto

I don't expect any changes in the traces format, but it's good to stay fairly up-to-date.

Diff: open-telemetry/opentelemetry-proto@a17f202...main

[trexx]

I take it that upgrading the collector dependency will also allow enabling TLS on the otlp receiver?
When I attempt to add the necessary TLS configuration in 1.2, Tempo distributor complains about invalid configuration.

[annanay25]

The collector was updated in the following PRs

• Update opentelemetry collector to v0.40.0 #1142
• Add gogoproto marshalling/unmarshalling to opentelemetry structs #1214

Should we rename this issue (to only update the proto) and move it into the next milestone?

[yvrhdn]

I'm not sure if we want to bother updating the proto. OTLP traces is declared stable so not much has changed.
These are changes between our version and main: open-telemetry/opentelemetry-proto@a17f202...main

Maybe we can look into this when we work on new backend formats?