Application Insights ASP.NET Core SDK by default reads application's IConfiguration and all properties of ApplicationInsightsServiceOptions from configuration

[rajkumar-rangaraj]

Addressing Issue: #1882

Changes

• Modified DefaultApplicationInsightsServiceConfigureOptions.cs to inject IConfiguration from an application and added the same to configurationbuilder
• Modified ApplicationInsightsExtensions.cs to bind configuration values to ApplicationInsightsServiceConfigureOptions

Checklist

• I ran Unit Tests locally.
• CHANGELOG.md updated with one line description of the fix, and a link to the original issue if available.

For significant contributions please make sure you have completed the following items:

• Design discussion issue #
• Changes in public surface reviewed

The PR will trigger build, unit tests, and functional tests automatically. Please follow these instructions to build and test locally.

Notes for authors:

• FxCop and other analyzers will fail the build. To see these errors yourself, compile localy using the Release configuration.

Notes for reviewers:

• We support comment build triggers
  • /AzurePipelines run will queue all builds
  • /AzurePipelines run <pipeline-name> will queue a specific build

[TimothyMothra]

@cijothomas friendly reminder, please put this PR at the top of your todo list.

[cijothomas]

@cijothomas friendly reminder, please put this PR at the top of your todo list.

Yup. Will review this shortly.

[cijothomas]

Thanks Raj. Looks good.
Requesting a minor (but important) change:

1. We need to test the WorkerService as well. It was already reading IConfiguration from user, but was never binding it to AIServiceOptions. Now, we added binding. But this portion is not tested.

2. Please set 30 mins so we can do a manual testing with this PR. Unit tests should cover everything, but this is significantly huge so we can afford to spend some time manual testing together.

[cijothomas]

Thanks Raj!
Lets open an new issue in Github to describe the new behavior. This PR is addressing a bunch of issues, so its easy if we have a new issue just describing the exact change, and have it linked in changelog.md.