Package references updates

[JunTaoLuo]

Addresses item in dotnet/aspnetcore#19254

As we discussed previously, we wanted to understand the changes in out package graph and make appropriate announcements. I made a quick analyzer that found the following.

I've noticed that dotnet/runtime does a few things differently:

1. If no code from a package dependency is actually used, it is not included as a dependency in the package produced. This can lead to breaking changes.
2. If code from a transitive dependency is used, it will be included as a direct dependency. Though this results in a different set of dependencies listed in the package, I believe it does not cause a breaking change, especially given that we service all of those dependencies.

I've opened this as a PR so we can review each change if necessary. However, I don't plan to check this in.

[JunTaoLuo]

In this case, it turns out only code from M.E.Configuration.Abstraction is used. So the package removed the M.E.Configuration dependency and added a M.E.Configuration.Abstractions dependency.

[JunTaoLuo]

This is a change we noticed during our ingestion. Along with the change in M.E.Options

[JunTaoLuo]

I just checked, these were in the previous closure as well since Microsoft.Bcl.AsyncInterfaces included a reference to it so this is a false positive. I didn't include that package in the set of packages I was analyzing. The same goes for M.E.Hosting.Abstraction.

[ericstj]

These all look reasonable. Thank you for analyzing this.

[analogrelay]

Assuming none of the assemblies in these packages were actually used, this looks fine to me.

[analogrelay]

Is this because the type is just part of .NET Framework 4.6.1? (@ericstj ?)

[ericstj]

Yes

[JunTaoLuo]

Announcement made in aspnet/Announcements#415