Remove SDK dependency from auto-instrumentation

[codeboten]

Description

This change moves the component initializing code that needs the SDK into the SDK's configuration module. This is then loaded in the auto instrumentation via entrypoint to ensure other SDKs can implement their own.

NOTE: the dependency from the SDK on the instrumentation package is only needed if we choose to include the configurator interface in the SDK. There is a following PR coming that propose this could be moved into a configure_distro entrypoint. This future PR will also include an opentelemetry-distro package that configures the defaults.

Fixes #1421

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Does This PR Require a Contrib Repo Change?

• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been updated
• Documentation has been updated

[NathanielRN]

This could be just a function as well right?

Suggested change

	class Configurator:
	def configure(self):
	initialize_components()
	def configure():
	initialize_components()

and then in sitecustomize.py it would just be entry_point.load()()

[ocelotl]

Hmno, the load method will yield the object that is pointed by the entry point value, in this case opentelemetry.sdk.configuration:Configurator which is a class. An entry point can point to a method, or some other object, but what this approach that we have been using is to declare an ABC in the API that mandates that certain method is implemented in order for the entry pointed classes to have it and run it when sitecustomize is invoked.

[NathanielRN]

I see, having the ABC would be helpful. Where would that definition go though? In opentelemetry-instrumentation or opentelemetry-sdk?

Does that mean that the other package would have to take the package that includes the ABC as a dependency?

(The opentelemtery-sdk to have its Configurator up to requirements and the opentelmetry-instrumentation to be able to validate classes it finds through the entry points)?

[ocelotl]

The ABC will be in the API.

[ocelotl]

No, wait, that ABC should be in opentelemetry-instrumentation. Sorry 😅