fix: respect defaultValue when arg is AstNodeType.EMPTY

[marcin-kordas-hoc]

Problem

When a user writes an empty argument (e.g. =VLOOKUP(2,A1:B3,2,)), the parser
produces AstNodeType.EMPTY which evaluates to EmptyValue (a Symbol sentinel).

The guard in FunctionPlugin.coerceArgumentsToRequiredTypes checked only for
undefined, so EmptyValue passed through and was coerced to 0/false instead
of using the parameter's declared defaultValue.

Affected functions: any plugin parameter with defaultValue ≠ 0/false
(e.g. LOG base=10, VLOOKUP/HLOOKUP sorted=true, MATCH matchType=1, ADDRESS abs=1).

Fix

In FunctionPlugin.coerceArgumentsToRequiredTypes: when the runtime value is
EmptyValue and the parameter declares an explicit defaultValue, substitute
defaultValue instead of passing EmptyValue to type coercion.

Tests

Regression tests in companion PR in handsontable/hyperformula-tests
(branch fix/empty-default-value): covers VLOOKUP, HLOOKUP, MATCH, ADDRESS, LOG.

---

Note

Medium Risk
Touches shared function-argument coercion used by all formula plugins, so behavior changes may surface broadly, but the change is narrow and gated to EmptyValue with an explicit defaultValue.

Overview
Fixes argument coercion so explicitly empty arguments (parsed as AstNodeType.EMPTY → EmptyValue) are treated like “missing” when a parameter defines a defaultValue.

In FunctionPlugin.coerceArgumentsToRequiredTypes, EmptyValue now substitutes the corresponding defaultValue (when provided) before type coercion, preventing empty trailing args from being coerced into 0/false for functions like LOG, VLOOKUP/HLOOKUP, MATCH, and ADDRESS.

^{Written by Cursor Bugbot for commit f68ecd8. This will update automatically on new commits. Configure here.}

[marcin-kordas-hoc]

Wrong origin