Report statement errors

[phr34k]

Initial changes to improve error reporting in combination with preprocessor directives. The intent of this changeset is the modify glslang in a way it reports location where the statement origionally begin, so that any syntax errors can report that location primarilly and/or report the type of statement.

All unit tests passed locally

This changeset modifies the glslang in the following ways:

• modified the standalone glslang to include --report-statements feature toggle to enable functionallity optionally
• modified the function signature of parseHelper::parserError to add in the location
• modified the grammar to use bison custom syntax error reporter
• modified the parserContext to keep track of some extra meta data w.r.t. statement and scope boundaries
• modified the grammar to track the statement/scope boundaries either trough bison "subroutines" or mid-action rules

Example

#line 200 
layout( .... ) fragColor1
#line 500 
layout( .... ) fragColor2:

See https://github.com/KhronosGroup/glslang/issues/3544

[CLAassistant]

All committers have signed the CLA.

[arcady-lunarg]

This looks interesting, but it's going to take a little while for me to give this a proper review.

[phr34k]

Sounds good, surely there are some corner cases that can have been easy to miss, but I hope it's a small step in the right direction!