Allow Traditional WebJobs to run as Azure Functions

Will you be providing the ability to run traditional WebJobs as Azure Functions, for instance Queue/Blob/EventHub triggered events?

Or, as what may be more likely given a [recent blog post](https://blogs.msdn.microsoft.com/appserviceteam/2017/03/16/publishing-a-net-class-library-as-a-function-app/ "Publishing a .NET class library as a Function App"), will I be able to publish a class library that allows all the same extensibility as through the WebJobs SDK.

Where I'm coming from is this. I like the flexibility of Web Jobs (e.g. to extend the logging to a [different logging framework](https://github.com/JSkimming/serilog-extensions-webjobs "Serilog.Extensions.WebJobs")), but I also like the Consumption Plan pricing model of Functions.

I appreciate there will have to be some limitations, for instance continuously running jobs would not work with the Consumption Plan, but some of the extensibility points may still be a possibility.

The issue names no files, tests, or implementation entry points. Start by reviewing the Azure Functions host and WebJobs SDK extensibility model, then determine which Queue, Blob, EventHub, and class-library scenarios are supported. Done would require a decided scope and corresponding implementation or documented limitation.

Written by the indexing model from the issue text.