fix(napi): validate fn for Option<T>

[Brooooooklyn]

• Close NAPI doesn't check for types received by a function #1218

[Hywan]

Passing undefined for an Option<String> produces the following error:

Expect value to be Option<String>, but received Undefined

If we pass null, it works. The goal of Option<T> is to have optional parameter, kind of, so passing null doesn't help :-). Is it possible to treat undefined as a valid None equivalent?

Edit: since null and undefined are supported in FromNapiValue and ToNapiValue in Option<T> implementations, I took the liberty to open a PR, #1228 to update its ValidateNapiValue implementation.