Support non-convention VM resolution

[MeirionHughes]

when bar.ts is:

useView("foo.html")
export class Bar{}

and ray.ts is

export class Ray{
  getViewStrategy() {
    return 'foo.html';
  }
}

then foo.html should resolve to view-models ["bar.ts", "ray.ts"] and perform type-checking against both.

[petronellius]

Please, support also scenario when global custom view location convention is used by overriding ViewLocator.prototype.convertOriginToViewUrl method. In our project views and viewmodels differ with names (e.g. title.html and titleVM.ts).