Don't inject bindings at manifest generation for worker projects.

[mitchdenny]

Fixes #743

We will now scan the project file Sdk to ensure that it is a web project, and only then will we automatically inject the service bindings.

[davidfowl]

Can we instead enrich IServiceMetadata generation?

[mitchdenny]

Can we instead enrich IServiceMetadata generation?

Funny you say that ... I was thinking exactly the same thing this evening as I was making dinner!

[mitchdenny]

Actually we need to support the scenario where multiple SDKs are referenced. Uncommon, but possible.

[davidfowl]

@mitchdenny when you are back can you prioritize this one?

[mitchdenny]

@davidfowl I'm not so certain looking at the SDK being used is good indicator of whether a project should have bindings automatically generated. I'm thinking it might be better to look at launchSettings.json and determine whether a app URL is present or not.

Updated to code to do this for now since I think it is actually safer, and I think the MSBuild path might be a bit of a dead-end if my understanding of what we can get out of the <MSBuild /> task is correct (and even then I am not convinced its desirable).