Enhance segregation of requirements and implementation

This change contains one enhancement and three bug fixes.

Enhancement:
Output parameters in a decision table have been previously ignored in scenarios.
Now they are available in the scenario. This allows to better segregate requirements from the implementation. See the test page "SegregationOfRequirementsAndImplementation" for details.

Bug Fixes:
1. StackTraceEnricherTest fails under Windows if folder contains spaces
This fixes a problem with this junit test under windows if a folder name
contains a space. In the identified location the space is replaced with
"%20" will classpath has spaces.  This fixes this problem by replacing
all "%20" with a space in the location. As the test already replaces /
and \ one more replacement should not break anything further.

2.  Allow Scenarios with parameterized style but with empty paramter names

This fixes a bug whith parameterized style scenarios where the paramters
have no name like:

|scenario | Division _ _ _ | numerator, denominator, quotient|

Previously this only worked with two spaces between each underscore. The
regex pattern has been fixed to work now with only one space.
  
3.  SyntaxErrors are now counted in the TestSummary

A table has a syntax error during parsing. E.g. a scenrio without a
name:

|scenario|

Also the table was marked as FAILED the test summary had zero failures.
Three things have been fixed now:
3.1. instead of FAILED the table is shown as ERROR/EXCEPTION
3.2. The test summary shows 1 exception
3.3. The error text which contains HTML is printed correctly (with the
HTML formatting)  in the table