[FLINK-33255] [table] Validate argument count during type inference

[bvarghese1]

• Previously, TypeInferenceOperandInference was not validating argument counts which led to bugs like FLINK-33248
• This commit adds a check to validate argument count and throws an exception if the argument count doesn't match the expected number of arguments

What is the purpose of the change

Validate argument count during type inference to avoid bugs like [FLINK-33248]

Brief change log

• Adds a check to validate argument count and throws an exception if the argument count doesn't match the expected number of arguments
• Also leads to better error messages

Verifying this change

This change added tests and can be verified as follows:

• Added test to verify a ValidationException message is seen when functions are invoked without arguments
• Updated existing function tests with improved error message

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• 678be13 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[dawidwys]

some last suggestions from my side.

For the future. Could we create separate commits if we fix multiple issues? I could see this split into two separate commits:

1. Improve exception message for signature mismatch
2. Validate argument count in TypeInferenceOperandInference

[dawidwys]

LGTM. Thank you for this really nice improvement @bvarghese1 ! I think caring about exception messages is often underappreciated.