prevent EFM/GFM code from executing with EBA/EIOPA validation
Pull request 41:

This request was partially merged to the master branch, with a tentative change for the evaluation output (need discussion with both EIOPA and Greg's user):

1) instead of output expression and variables, and the formulaVarSetExprInError in pull request, at this moment there are 3 options, formulaSatisfiedAsser (trace satisfied assertions as info severity), formulaUnsatisfiedAsser (trace unsatisfied assertions as info severity), and formulaUnsatisfiedAsserError (trace unsatisfied assertions as error severity).

2) the formula label, or id (if no label), or xlinkLabel (if neither) is shown (the label includes the Taxonomy Architect expression for the formula in terms of filing indicator row/col, which is more comprehendible to business user than the xPath expression (only for techie).

3) the variables output for the moment are all bound variables, not just those in the assertion expression, because they may be an important part of filters and preconditions. Fallback values are also indicated. Sequences are handled.

I expect this to be refactored and evolved after initial comment, so pull request #41 is left open.