Add validation for unsupported type/identifier/commands

[ykmr1224]

Description

• Add validation for unsupported type/identifier/commands
  • Those grammars are defined but considered unsupported

Related Issues

#3185

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dai-chen]

Just curious if it's defined as unsupported in grammar for all data sources, why we still want them in grammar?

[YANG-DB]

@ykmr1224
can we auto-generate the SQLGrammarElement & PPLGrammarElement automatically using the ANTLR files ?

[ykmr1224]

Just curious if it's defined as unsupported in grammar for all data sources, why we still want them in grammar?

Those are coming from Spark SQL grammar, which we don't want to touch considering when we upgrade Spark version.
I'm not quite sure the original intention in Spark repository, but it might be to raise error as unsupported type instead of parse error.

[ykmr1224]

@ykmr1224 can we auto-generate the SQLGrammarElement & PPLGrammarElement automatically using the ANTLR files ?

I considered that option initially, but the grammar file contains lots of elements, where same grammar element can be define as multiple way in g4 file. That could lead to very redundant configuration. Also the error message would need to use node name in g4 file, which would become very unclear for users.