JFR: Fail-fast mode when constants cannot be resolved

A reoccurring problem in JFR are constants, i.e. threads, classes and methods, not being resolved properly. Users will see this as a field value being null (N/A), or NPE if application code depends on the value not being null.

Today, we can track those occurrences with -Xlog:jfr+system+parser=info, but if we had a fail-fast mode enabled during testing, we would find the problem closer to when it's introduced.

It could be an assert, or a system property, that is checked and an InternalError is thrown if an unresolvable value is found.