Add declarative configuration prototype

[ocelotl]

TODO:

• Generate model code from JSON schema config: generate model code from json schema #4879
• Core Loading & Validation config: load and validate generated config models #4898
• Update to 1.0.0 spec feat(config): upgrade OTel configuration schema to v1.0.0 #4965
• Resource & Propagator Creation feat(config): add resource and propagator creation from declarative config #4979
• TracerProvider Creation feat(config): Add TracerProvider support for declarative config #4985
• MeterProvider Creation feat(config): Add MeterProvider support for declarative config #4987
• LoggerProvider Creation feat(config): Add LoggerProvider support for declarative config #4990
• Process resource detector feat(config): add process resource detector support for declarative config #5001
• Host resource detector feat(config): add host resource detector support for declarative config #5002
• Service resource detector feat(config): add service resource detector support for declarative config #5003
• Container resource detector feat(config): wire container resource detector via entry point loading #5004
• Pull metric reader support feat(config): add pull metric reader support to declarative config #5216
• Metric producer support feat(config): add metric producer support to declarative config #5073
• composite samplers Add support for composite samplers in declarative config #5201

Loading of third party componets:

• Update generation logic to support additional fields feat(config): add additionalProperties support to generated config models #5131
• Generic resource detector plugin loading feat(config): generic resource detector plugin loading for declarative config #5129
• Generic exporter plugin loading feat(config): exporter plugin loading via entry points for declarative config #5128
• Generic propagator plugin loading feat(config): propagator plugin loading via entry points for declarative config #5098
• Generic sampler plugin loading feat(config): sampler plugin loading via entry points for declarative config #5095
• Convert factory functions to accept raw dicts from YAML loader feat(config): recursively convert parsed dicts to typed dataclasses in loader #5269
• Unify declarative and env-var configuration through a shared SDK orchestrator feat(config): unify declarative and env-var configuration through a shared SDK orchestrator #5126
  • `configure_sdk` orchestrator (Phase 1) feat(config): add configure_sdk orchestrator for declarative config #5270
  • env-var-to-config adapter (Phase 2)

Fixes

• Fix deflate compression support for HTTP exporters fix(config): allow deflate for OTLP HTTP exporters #5075

Finalise API

• Complete Integration & Public API
  • Honor `OTEL_CONFIG_FILE` env var in the SDK configurator feat(config): honor OTEL_CONFIG_FILE in the SDK configurator #5271
  • Promote `configure_sdk` / `load_config_file` to a non-underscore public namespace feat(config): add public opentelemetry.sdk.configuration namespace #5276

[codeboten]

@open-telemetry/python-maintainers hello! i'd like to take on the work to implement a prototype for declarative configuration in Python. What's the best way to do this? Would it be best to take over #3632, or best to start fresh?

One thing I've found helpful in the go implementation was to break things up in smaller PRs to get things moving. Let me know what you would all prefer!

[MikeGoldsmith]

Hey all - I'm gonna be working with @codeboten to add the OTel config implementation to Python.

I've broken out the implementation into steps to try keep it small and manageable:

1. Generate model code from JSON schema - Alex's PR: config: generate model code from json schema #4879
2. Core Loading & Validation
3. Resource & Propagator Creation
4. TracerProvider Creation
5. MeterProvider Creation
6. LoggerProvider Creation
7. Complete Integration & Public API

Does this sound like a good plan for you all?

cc @open-telemetry/python-maintainers