Prevent logger recursion during startup

[delner]

When Components are built, they sometimes log messages to Datadog.logger. If this happens, logger is not yet built/resolved, so it will lazily build another, triggering yet another log message and forming a recursive loop.

A simple way around this is to have some kind of default logger when components have not been initialized, but yields to the configured logger once its been built/configured.

[delner]

This bug manifested while building my profiling autostart feature because at the end of the components build process, the profiler would be started which would trigger a log message, which would get the logger (which was not yet set), which would trigger another component build, resulting in the loop.

Maybe another way to work around this is to start components after its been set on the @components variable. This would sidestep the log messages in the startup phase, but would not address log messages in the initialization phase.

[marcotc]

Is there a practical way to test this change?

[delner]

Maybe you could test to see if the default logger gets replaced by the logger from the components? Otherwise all this does is prevent a stack overflow, but I'm not sure if there's a practical test for that.

[marcotc]

I think we should protection around removing this block in the future, we can currently do that without any impact on CI.