RemoveSuperMethodsPass makes an unsafe assumption

RemoveSuperMethodsPass tries to remove methods that are just pass-through calls to a super class method.

e.g.
class A {
foo(a, b) { .. do something here ..}
}

class B extends A {
foo(a, b) { super.foo(a, b); } // remove this
}

These usually exist in order to tweak the return type of the child class method.

The trouble is that the pass makes the assumption that the parent and child class methods have the same number and order of arguments without actually checking this.

class A {
foo(a, b) { .. do something here ..}
}

class B extends A {
foo(a) { super.foo(a); } // this gets removed incorrectly
}

// Should end up calling A.prototype.foo.call(this, 1),
// but removal causes call to A.prototype.foo.call(this, 1, 2).
new B().foo(1, 2);