chore!: deprecate DD_CALL_BASIC_CONFIG

[mabdinur]

Deprecate DD_CALL_BASIC_CONFIG configuration.

This change removes all invocations of logging.basicConfig from tracing instrumentation: #3168.

Checklist

• Added to the correct milestone.
• Tests provided or description of manual testing performed is included in the code or PR.
• Library documentation is updated.
• Corp site documentation is updated (link to the PR).

[brettlangdon]

we shouldn't remove from here yet

[brettlangdon]

Suggested change

	ddtrace will no longer handle basic configuration of a logging system. `logging.basicConfig()` should be called in a client application.
	ddtrace will no longer handle basic configuration of a logging system. ``logging.basicConfig()`` should be called in a client application.

[brettlangdon]

I wonder if we can state more simply:

ddtrace will no longer call logging.baseConfig() on startup.

[brettlangdon]

🤔

I am not sure we can handle this with a deprecation actually. Since we do this by default we are basically going to add a warning log on every startup even when the user does nothing.

We might be better off just making the change on the 1.0-dev branch and have it as an upgrade note and we can document in any migration guide.

We could maybe deprecate the DD_CALL_BASIC_CONFIG env variable? But not sure if it is fully necessary since most people use it to disable calling basic config, so should not have any impact on upgrade.

cc @Kyle-Verhoog what do you think? is there another deprecation approach I am not thinking of?

[mabdinur]

I'll close this PR