[new-parser] Match EOF at the end of the compilation unit

[yurloc]

• Fixes [new-parser] Parser should expect the final EOF, otherwise it can stop prematurely and report no error #5929.

Without the EOF, the parser has no incentive to continue processing input once it encounters a "broken" DRL statement keyword.

For example, if there is a typo in the import statement (impot), the parser is simply unable to match drlStatement and it "gracefully" quits without reporting any error. Explained in more detail at https://github.com/antlr/antlr4/blob/master/doc/parser-rules.md#start-rules-and-eof.

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request and downstream checks

  • Push a new commit to the PR. An empty commit would be enough.

• for a full downstream build

  • for github actions job: add the label run_fdb

• for Jenkins PR check only

  • If you are an ASF committer for KIE podling, login to Jenkins (https://ci-builds.apache.org/job/KIE/job/drools/), go to the specific PR job, and click on Build Now button.

[yurloc]

@mariofusco @tkobayas @gitgabrio please review.