update otel dependencies to v1.27.0 and v0.52.0

[dependabot]

Directly update:

• go.opentelemetry.io/otel/* from v1.26.0 to v1.27.0
• go.opentelemetry.io/contrib/* from v0.51.0 to v0.52.0

Indirectly update:

• google.golang.org/protobuf from v1.33.0 to v1.34.0

This update breaks some of our existing otel grpc interceptors, but in return allows us to use the newer grpc StatsHandler mechanism, while still filtering out health-check requests.

Fixes #7235

[aarongable]

Let's have this PR update go.opentelemetry.io/contrib to v0.52.0 at the same time. That's part of the same bundled release, and contains the change we need to finish #7235

[beautifulentropy]

@dependabot rebase

[beautifulentropy]

Let's have this PR update go.opentelemetry.io/contrib to v0.52.0 at the same time. That's part of the same bundled release, and contains the change we need to finish #7235

After spending some time on this it appears that an update to v0.52.0 is going to be a heavy lift that should happen in its own PR. Upgrading this dependency necessitates an update to several others and ultimately breaks the build due to an otel schema change:

Dependencies:

	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.52.0
	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.52.0
	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.27.0
	go.opentelemetry.io/otel/sdk v1.27.0
        google.golang.org/protobuf v1.34.1

Build issue post go mod tidy && go mod vendor:

# github.com/letsencrypt/boulder/grpc
grpc/server.go:157:66: cannot use filters.Not(filters.HealthCheck()) (value of type otelgrpc.Filter) as otelgrpc.InterceptorFilter value in argument to otelgrpc.WithInterceptorFilter

Fix for build issue:

	options := []grpc.ServerOption{
		grpc.Creds(creds),
		grpc.ChainUnaryInterceptor(unaryInterceptors...),
		grpc.ChainStreamInterceptor(streamInterceptors...),
		grpc.StatsHandler(otelgrpc.NewServerHandler(
			otelgrpc.WithFilter(
				filters.Not(filters.HealthCheck()))),
		),
	}

Starting service remoteva-a
16:00:05.054880 3 remoteva 6MuMzQY [AUDIT] Could not create OpenTelemetry resource: conflicting Schema URL: https://opentelemetry.io/schemas/1.25.0 and https://opentelemetry.io/schemas/1.24.0
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1000 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1001 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1001 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1001 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1000 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1001 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1000 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1001 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 1000 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 885 ms
health checking rva.boulder (localhost:9897)
health checking rva.boulder (localhost:9897): grpc.health.v1.Health.Check timed out after 0 ms
16:00:15.045724 3 health-checker 7d6YxQY [AUDIT] timed out waiting for localhost:9897 health check

If you find a way to do this without the heavier lift, I'm all for it, but I'm not seeing an easy win here.

[aarongable]

I'll do it later today. I don't see any point to upgrade to 1.27 here without getting the accompanying 0.52 upgrade that we actually want, and the schema URL is just the same thing as I fixed in the previous PR here.

It sucks that these packages are structured such that dependabot can't simply update them correctly.

[aarongable]

Okay, updated the PR to also update the other dependencies, added the fixes for the API breaking changes, and updated the commit description. PTAnotherL!

[beautifulentropy]

I'll do it later today. I don't see any point to upgrade to 1.27 here without getting the accompanying 0.52 upgrade that we actually want, and the schema URL is just the same thing as I fixed in the previous PR here.

It sucks that these packages are structured such that dependabot can't simply update them correctly.

Neat, I'm happy you were able to figure out the schema URL issue.