Arg counts, types not checked on custom commands

[fmoo]

What is the current behavior?

When using a <> in a .yarn file, calling a custom command with the incorrect number or types on command arguments are not indicated as errors on in the Issues tab.

Functions behave correctly.

Please provide the steps to reproduce, and if possible a minimal demo of the problem:

1. Implement a basic custom command that takes one int as an argument, e.g.,

runner.AddCommandHandler<int>("Log", (num) => Debug.Log(num));

2. Call it in .yarn with no args
3. Call it in a .yarn with two args
4. Call it in a .yarn, but pass a string

e.g.,

<<Log>>
<<Log 1 2 3>>
<<Log spam>>

What is the expected behavior?

The above examples should show an issue in the "Issues" tab in vscode.

Number "4" might be trickier, since it's probably ok to pass numbers as unquoted strings for a command that accepts strings.

Please tell us about your environment:

• Yarn Spinner Version: 2.2
• Extension Version: 2.2.15
• Unity Version: 2021.1.18f1

Other information

[fmoo]

Also repros on vscode extension v2.2.40