Make SemconvStability config work without GlobalOpenTelemetry

SemconvStability currently resolves declarative config from GlobalOpenTelemetry.getOrNoop() during static initialization. This means library instrumentation users who pass an OpenTelemetry instance directly to an instrumentation builder do not get semconv stability config from that instance unless they also install it globally.

Library instrumentation should be able to honor semconv stability config from the supplied OpenTelemetry instance, without requiring GlobalOpenTelemetry.set(...).

The affected settings are:

• general.semconv_stability.opt_in
• general.semconv_stability.preview
• common.v3_preview

Investigated a bit: would likely mean a new pattern of injecting OpenTelemetry (or maybe better ConfigProvider) into all of the
Extractors. Tracking issue for ConfigProvider stability (see https://github.com/open-telemetry/opentelemetry-java/issues/7961.

Note: I don't think this needs to happen for 3.0.

Start by tracing SemconvStability's static initialization and the Extractors mentioned in the issue, then inspect how instrumentation builders pass an OpenTelemetry instance. Done means the three listed semconv stability settings are honored from that supplied instance without requiring GlobalOpenTelemetry.set(...).