ConfigurableSurefire interpreter should return test step statuses for BDD cucumber tests

Related to this issue
Macro feature is explained in the "mother" issue too.

I put the status as UserStory for QA team, to focus the attention here, on the fact that the code to publish cucumber test step is implemented in ConfigurableSurefireParser, with associated configuration, that, in my opinion, needs to be a little more tested that the feature for Robot Framework.

The current implementation (will be re-architecture when we have more time, in this issue is :

• a key supportsStepStatuses with value true has been added in the configuration file internal-parsers.yml
• if the ConfigurableSurefire finds the key with value true -> the code to parse cucumber .xml report file is launched, and step statuses has send to the publisher
• if the key does not exist in file, or has another value than true, the code to find and publish step execution statuses is not executed. Behaviour should be as it was before.

Error management:

• if the xml report does not contain the stdout in which the step statuses are, a WARNING log is displayed
• if the xml report does contains the step statuses, another WARNING log is displayed
• if a unknown statuses is found in report (anything that is neither PASS, nor FAIL, nor SKIPPED), another WARNING log is displayed.

In all cases, an empty map of step statuses is send to the publisher, and no steps are displayed in Squash TM.