Proposal: Support well known resource detectors

[RassK]

What

Support well known resource detectors automatically.

List:

• [x] Docker
• [x] Azure
• [ ] AWS[^1]
• [ ] Kubernetes
• (Add your thought here...)

[^1]: Seems this package has mixed up instrumentations and resources? Could be worth checking before implementing.

[pellared]

I think that the user can get these resources using the OTel Collector. I am not sure if we need to have it in auto-instrumentation (more dependencies, bigger package, more maintenance).

[Kielek]

AWS packages are subject to change under contrib repository (including renaming). If we need only part of this, we could probably extract resource package.

[pjanotti]

SIG meeting:

• Needs to be configurable similar to what is done for instrumentations (fine and coarse level control)
• Short run: add "low dependencies" detector: docker first and AZ when package is ready
• Medium term: decide about how to support more complex packages (e.g.: AWS)

[Kielek]

For now, we supporting following resource detectors:

• AZUREAPPSERVICE
• CONTAINER
• HOST
• PROCESS
• PROCESSRUNTIME.

If there is a needs for others, please create separate issue/PR. Closing.