Determine lowest compatible `opentelemetry-distro` (`-api`, `-sdk`) version

[sentrivana]

Version pinning can create issues for folks. We should be as lenient as possible.

We'll be testing our POTel setup with latest OTel packages. Before we switch to POTel and introduce these packages in setup.py for the generic install target (i.e., not [opentelemetry] or [opentelemetry-experimental]), we should dedicate some time to figure out if we need a lower bound on the version.

Once we're confident our OTel setup works well enough with the latest versions of OTel dependencies, retest with lower versions to find out how we work with older versions. On a case by case basis, fix things if easy enough, or decide to introduce a lower bound.

Note: This also affects what Python versions we can support.

[antonpirker]

Opentelemetry dropped support for Python 3.7 in version 1.23.0 / 0.44b0 on Feb 23, 2024.

So if we want to keep Python 3.7 the highest supported Otel version would be 1.22.0 / 0.43b0.

(1.XX.0 version numbers are for opentelementry-sdk, opentelementry-api, opentelementry-proto. 0.XXb0 version numbers are for opentelemetry-distro)

[antonpirker]

Our decision for Sentry using OpenTelemetry under the hood:

The Sentry SDK will still keep support for Python 3.7+.

In case users are on Python 3.7 they can use newest Sentry but have to use the OpenTelemetry libraries <= 1.22.0 / 0.43b0.

In case users are on Python 3.8+ they can use newest Sentry and OpenTelementry.

Either way, we want to make sure that the lower bounds of the OpenTelementry dependencies are as low as possible.