[v15] chore: Bump github.com/sigstore/cosign/v2 to 2.2.4

[codingllama]

Manual backport of #40485 to branch/v15.

Changelog: Updated cosign to address CVE-2024-29902 and CVE-2024-29903

[codingllama]

This touches quite a lot of deps, so I gotta say it makes me a bit uneasy. WDYT?

[tigrato]

This touches quite a lot of deps, so I gotta say it makes me a bit uneasy. WDYT?

These CVEs might affect our use-case for cosign and are mainly important for users that use custom registries. If an attacker gains the ability of overriding the image they can cause denied of service.
I think we should go ahead and update them.

What do you think @hugoShaka ?

[hugoShaka]

I'm in favor of doing the update to fix the CVE, especially because the updater doesn't have memory limits by default.

I walked through all the changelogs for 0.x direct dependencies are did not find anything obvious that would break for us.

However, this PR causes an OTEL schema bump, and we end up with two conflicting schemas.

=== Failed
=== FAIL: lib/observability/tracing TestTraceProvider/not_sampling_prevents_exporting (0.01s)
    tracing_test.go:363: 
        	Error Trace:	/__w/teleport/teleport/lib/observability/tracing/tracing_test.go:363
        	Error:      	Received unexpected error:
        	            	1 errors occurred detecting resource:
        	            		* conflicting Schema URL: https://opentelemetry.io/schemas/1.21.0 and https://opentelemetry.io/schemas/1.24.0
        	Test:       	TestTraceProvider/not_sampling_prevents_exporting

[codingllama]

Yes, there are problems with otel, I'll chase those in the near future.