Add test coverage for typed and range err

[JckXia]

PR aims to close #981, #984 and #1271.

Adds test for TypeError and RangeError, as well as some validation logic for the napi_value object we pass to the base TypeError and RangeError ctor. The question is whether we want to crash the application when the napi_value passed isn't a js TypeError, or if we want to emit some type of warning instead.

[legendecas]

I'd suggest avoiding type checks in type wrapper constructors for the following reasons:

1. These are error classes and we should avoid throwing in their constructors as they are likely to be used in error-handling paths already.
2. Calling into JavaScript can throw arbitrary errors too.
3. We don't do type checks in other node-addon-api type wrapper constructors, and type check is not performance free.

Instead, I'd suggest adopting the approach introduced in #1281, allowing people to opt-in for the type check.

[JckXia]

@legendecas Thank you for your explanation! Will update my changes.