Support Python SDK 3.0.0

[antonpirker]

[work in progress]

Update the code so it works with the upcoming major release of the Sentry Python SDK 3.0.0.

Sentry SDK 3.0.0 has massive changes on how the data flows through the SDK compared to 2.x. (3.0 uses Opentelementry under the hood to create spans)

Some APIs in 3.0 is not backwards compatible with 2.x so we need to change a lot of call sites.

What this PR does:

• change all .start_transaction() to .start_span() (without ever setting only_if_parent)
• replace span.set_data() with span.set_attribute() with the same params
• change one continue_trace() to the new context manager.
• change one scope.add_attachment() to sentry_sdk.add_attachment()
• replace scope.transaction with scope.root_span
• replace Span.containing_transaction with Span.root_span
• check that attributes in start_span() can NOT be a dict. (Note: It only had sample_rate set which is a float.
• moved sampled=False from assigning to a span into the start_span() call.
• replace custom_sampling_context with attributes parameter in @trace_func
• replace custom_sampling_context param in .start_span() with attributes
• remove custom_sampling_context everywhere in code base (given to spans)
• remove @metrics_noop decorator, because there are no metrics anymore only span.data, so we do not need it.
• remove helper src/sentry/utils/sdk.py::set_measurement() because it is not used in sentry.
• check that set_attribute() value is NOT a dict. See: Do not use dicts in .set_data().  #92720

Related, but split out in separate PRs:

• make sure traces_sampler works the same as before (check for sample_rate) Done here: test: Add test for custom sample rates #93011
• Make all get_isolation_scope calls use the top-level API. Currently, some calls where we from sentry_sdk import Scope then call Scope.get_isolation_scope still need to be converted to the top-level API. Do this in a separate PR. Done here: Cleanup imports to always use the top level api. #93307
• check event["measurements"] places if those can be removed (because SDK does not support measurements anymore). split into: Remove usage of measurements in favor of span.data. #92718
• change set_span_data() to set_span_attribute() but check for value NOT be a dict. (split off into ref: Rename set_span_data to set_span_attribute #92946)
• replaced with sentry_sdk.init(dsn=...) with with sentry_sdk.new_scope() as scope: scope.set_client(sentry_sdk.Client(dsn=...)) in src/sentry/runner/main.py (split into ref: Use set_client to change DSN #92944)
• removed propagate_hub=True from ThreadingIntegration (ref: Remove propagate_hub to ThreadingIntegration #93016)
• removed minimetrics from the sentry codebase, because the metrics product was never released. (Remove minimetrics #93595)

requires https://github.com/getsentry/getsentry/pull/17553
requires getsentry/devenv#194
requires getsentry/devservices#277
requires getsentry/pytest-sentry#39
requires getsentry/sentry-docs#13939

[codecov]

❌ 3 Tests Failed:

Tests completed	Failed	Passed	Skipped
26647	3	26644	230

View the top 3 failed test(s) by shortest run time

tests.relay_integration.test_sdk::test_encoding[MONOLITH]

Stack Traces | 106s run time

#x1B[1m#x1B[31mtests/relay_integration/test_sdk.py#x1B[0m:98: in test_encoding
    assert event.data["project"] == settings.SENTRY_PROJECT
#x1B[1m#x1B[31mE   AttributeError: 'NoneType' object has no attribute 'data'#x1B[0m

tests.relay_integration.test_sdk::test_simple[MONOLITH]

Stack Traces | 116s run time

#x1B[1m#x1B[31mtests/relay_integration/test_sdk.py#x1B[0m:64: in test_simple
    assert event
#x1B[1m#x1B[31mE   assert None#x1B[0m

tests.relay_integration.test_sdk::test_recursion_breaker[MONOLITH]

Stack Traces | 116s run time

#x1B[1m#x1B[31mtests/relay_integration/test_sdk.py#x1B[0m:81: in test_recursion_breaker
    with pytest.raises(Exception):
#x1B[1m#x1B[31mE   Failed: DID NOT RAISE <class 'Exception'>#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[JoshFerge]

there seems to be a lot of unrelated changes in this PR?

[untitaker]

there seems to be a lot of unrelated changes in this PR?

are there? some new sdk-related tests, other than that it's a mass-replace