Instrumentation options

[jeremydvoss]

Description

Add new instrumentation_options field akin to Node's implementation. This will allow users to disable opt out supported instrumentations and enabled opt in preview instrumentations. Explicit configuration will take priority over env vars. In order to leave the door open for instrumentation configuration in the future, I have implemented a way to merge nested dictionaries. This way, a user can pass additional options and they will be merged with the defaults instead of entirely replacing them. See tests for more details.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

API changes are not detected in this pull request.