Resolves #4571

Changes:

1. Make the FES detect trailing undefined arguments
   Consider the following few examples

let r, g, b;
function setup() {
  let r = 50;
  color(r, g, b);
}

Here g and b are undefined. But earlier as color with only one argument was still a valid overload, the FES did not log a message. But as it is passed 3 arguments, it is likely that them being undefined is unintentional and so a message should be displayed.

Now it shows:
🌸 p5.js says: color() was expecting Number for parameter #1 (zero-based index), received an empty variable instead

🌸 p5.js says: color() was expecting Number for parameter #2 (zero-based index), received an empty variable instead

Similarly:

function setup() {
  let a = document.getElementById('nonexistant');
  select('hgg', a);
}

would not have logged an error before this, as the undefined argument is trailing and select(string) is a valid overload. A message here is important to let the user know that a is empty ( i.e notexistant was not found )

Now it shows:
🌸 p5.js says: select() was expecting String|p5.Element|HTMLElement for parameter #1 (zero-based index), received an empty variable instead.

Also for

let r;
circle(10, 10, r);

Earlier we used to get
🌸 p5.js says: circle() was expecting at least 3 arguments, but received only 2

Now it correctly shows:
🌸 p5.js says: circle() was expecting Number for parameter #2 (zero-based index), received an empty variable instead.

2. Pass the error type to the ValidationError constructor so that it could be accessed in tests
3. Add tests for the edge cases in FES misses error cases #2740
4. Add tests for detection of trailing undefined arguments

PR Checklist

• npm run lint passes
• Inline documentation is included / updated
• Unit tests are included / updated