NodeJS host.json file when invalid works locally but not when deployed

Since the azure functions core tools is trying to emulate Azure Functions I consider this a bug or an enhancement.

I created a function that used bindings for table storage, read & write and used http triggers for this. My host.json file was invalid and everything worked locally when it should not work locally.

I spent hours debugging this by deleting code, hardcoding variables etc to finally find out my host.json was invalid. The azure Functions App wasn't helpful when debugging this because it kept only showing a HTTP 404.

I had this in the host.json file:
````json
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[1.*, 2.0.0]"
}
````

When it should have been this:
````json
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[1.*, 2.0.0)"
}
````

I'm not sure how hard this would be to emulate correctly, but maybe a JSON Schema checker could do the trick.

No source file or test is named. Start by reproducing the invalid host.json behavior with Azure Functions Core Tools and trace how host.json is loaded locally. Done means invalid configuration is rejected locally with a useful diagnostic consistent with deployment behavior.

Written by the indexing model from the issue text.