Fix 9363: passing undefined or null to parameter destructuring

[yuit]

Fix #9363
This probably should be ported to release-2.0 as well.
Also, technically, it is actually fine to pass undefined or null if the --target is es5 (at least for the empty destructing case as we won't be emit the destructuring in the body) I think it is more consistent to error regardless of the --target. let me know if you think it should respect the target more

[shovon]

I'll admit, I was a bit careless when I wrote my comment in #9363.

I think my comment should be a part of a broader discussion about nullability of destructured parameters. I understand non-nullable types are slated for TypeScript 2.0, based on #185.

Maybe destructured parameters should be a non-nullable type by default?

[yuit]

@shovon @DanielRosenwasser and I discussed off-line, turned out there are some cases that we will have to consider

function foo({} = undefined) {}
foo(undefined)  // this should be an error as the initializer will get evaluted to be undefined

We think it will be a good idea to have a non-nullable type for destructuring. There are also this case that should be an error

var {} = undefined;
var [] undefined;

[yuit]

We should use slightly different approach to sovle the problem. Track the issue in #9429