Upgrade apex-parser version to 4.0.0

[adangel]

This upgrades apex-parser to the new version and adjust to the grammar changes (trigger block)

• https://github.com/apex-dev-tools/apex-parser/releases/tag/v4.0.0

This is not yet available in maven central (https://central.sonatype.com/artifact/io.github.apex-dev-tools/apex-parser/versions), so the build currently fails. I tested it locally.

This upgrade also contains a fix for typeof needed in pmd/pmd#4922 .

Note: For adapting to the trigger block changes, I naively put the body of the trigger in a List<Node>. I assume, the order is then the order how it is defined in the source, possibly mixed declarations and statements. The CompoundStatement is gone and with that also the scoping boundary... Not sure, if this is the best approach.

• Tests pass
• Appropriate changes to README are included in PR

[adangel]

@aaronhurst-google
apex-parser 4.0.0 is now in maven central - If you restart the CI build, it should be working now...

[aaronhurst-google]

LGTM

[aaronhurst-google]

Note: For adapting to the trigger block changes, I naively put the body of the trigger in a List. I assume, the order is then the order how it is defined in the source, possibly mixed declarations and statements. The CompoundStatement is gone and with that also the scoping boundary... Not sure, if this is the best approach.

For scope analysis, it would be very nice to be explicit about the boundaries. But this isn't lossy; the scope is still implied by the parent TriggerDeclaration. Just another case to handle. :)