Log error or warning for service versions that are ahead of host services

Whenever App Insights moves forward, we get a wave of customers that run into issues because we always lag behind. Same thing happens with .NET Core versions. This is especially problematic now that DI is available.

Can we throw an error or warning during service resolution if we see a type being requested that is ahead of the version that we're actually using? Being able to show a log like `You have registered or requested a service with a service type of ITelemetryInitializer v2.10.0, but the current Functions host references v2.9.1. Please reference this version...` would go a long way to preventing confusion.

See my comment here for details on one App Insights scenario: https://github.com/MicrosoftDocs/azure-docs/issues/35181#issuecomment-512288993

The payload names no files, tests, or entry points. Start by reading the linked Azure Docs comment and tracing service resolution in the Functions host; done means an agreed warning or error identifies requested service versions that are ahead of the host version and is verified for the described App Insights scenario.

Written by the indexing model from the issue text.