feat($compile): Allow ES6 classes as controllers with bindToController: true

[lgalfaso]

Modify $injector.invoke so ES6 classes would be invoked using new

Closes: #13510

[lgalfaso]

Do not know how to fix this flake in the tests

IE 9.0.0 (Windows 7) filters date should ignore falsy inputs FAILED
    Error: [$injector:modulerr] Failed to instantiate module ng due to:
    Out of memory

[gkalpak]

Is $scope needed here ?

[lgalfaso]

Not really, will remove it

[gkalpak]

LGTM

Something for a follow-up PR:
Maybe it's a good idea to avoid intializing the bindings prior to instantiating a class-based controller, since we know they won't be used (i.e. the return value will be different than self).

[lgalfaso]

@petebacondarwin do you think this should go into 1.5 ?

[bisubus]

@lgalfaso There's a significant problem with this approach, I've covered it in this comment and fought it in that extension (you may go by the implementation and see how clumsy it became with multiple checks and flags).

The source of the problem is that this

function isClass(func) {
  return typeof func === 'function'
    && /^class\s/.test(Function.prototype.toString.call(func));
}

will work for native classes and will fail for transpiled ones (with Babel).

[lgalfaso]

I am landing this as this PR already has enough to handle all current browsers that natively support class.

[lgalfaso]

@bisubus I am not sure how this affects Babel at all. The current mechanism that forces a this into the constructor function is indistinguishable for Babel as there is no support for new.target. Would it be possible for you to create a plunker that uses the latest snapshot and shows this issue?

[petebacondarwin]

This change caused IE9 to run out of memory.