Feature/yangkit complete validation

[ahuangfeng]

• Update antl4-runtime to 4.11.1
• force Java 11
• Allow not mandatory root schemas to not be present in the encoded message.
• Allow augmentation of mandatory nodes without "when" statements within the same module (errata; Andy reported that it should allowed when it is within the same module)
• Allow messages without the wrapper "data".
• Example of parsing ietf-interfaces.yang

[lllyfeng]

why force java 11? java 8 is the most popular.

[lllyfeng]

and I cannot merge this PR for some conflicts are not resolved.

[ahuangfeng]

and I cannot merge this PR for some conflicts are not resolved.

This PR #38 is to be merged after main branch is fixed (currently main is not compiling). We will rebase and fix the conflict when main is working again.

Regarding forcing java 11, I can rollback if needed

[lllyfeng]

and I cannot merge this PR for some conflicts are not resolved.

This PR #38 is to be merged after main branch is fixed (currently main is not compiling). We will rebase and fix the conflict when main is working again.

Regarding forcing java 11, I can rollback if needed

hi, I have published a new version,1.5.0, and the main branch has been fixed.

[cuihengch]

for those printed info, how about using record.getSeverity() instead of all as Error?

(so that other severities such as Warning etc. can be distinguished from here)

[lllyfeng]

only ‘Error’ means result is not ok,:)

[ahuangfeng]

Dear @lllyfeng ,
I updated the code and tested on my local validating ietf-interfaces.yang and ietf-telemetry-message.yang messages.
The CI has been updated to Java 11. The current maven project does not force any java version, so users can still use any version they want. However, antlr4-runtime needed to be updated to enable integration with the Kafka project.
Regards,
Alex