Use resolveSync on loader when available

[johnnyreilly]

Having boldly upgraded to enhanced-resolve v3 this seems to be causing issues for some people.

Given that webpack 2 comes with a resolveSync available on the loader it may make sense to roll back to the previous approach where we used enhanced-resolve v0.9 and in servicesHost.ts try to use the resolveSync (which will work for webpack 2) and fallback to the 0.9 one (for webpack 1).

In the longer term we'd then look to remove the dependency on enhanced-resolve entirely when webpack 2 is RTM'd. Hopefully this should resolve the following issues:

#421 #420 #417

[johnnyreilly]

Hmmm... This does not appear to be a go-er. The underlying resolver in webpack is not initialised.