MQE-1234 & MQE-659: StepKey in test result output and native XML comments

[okolesnyk]

Description

Fixed Issues (if relevant)

1. magento/magento2-functional-testing-framework#<issue_number>: Issue title
2. ...

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/verification tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)
• Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

[coveralls]

Coverage increased (+1.8%) to 56.211% when pulling bafc0c9 on MQE-1234-alex-edition into 3a77cc5 on develop.

[KevinBKozan]

Please create a verification test to test out the XML unsafe characters usecase specifically (< > & " ' etc)

Commit requested changes.

Commit latest fixes

[KevinBKozan]

Found an issue with both of these contents combined:
Create a suite with the following block:

<before>
    <!--COMMENT HERE-->
    <magentoCLI stepKey="STEPKEY" command="helloworld"/>
</before>

Then debug at ln 176 of GroupClassGenerator, it splits lines based on ; which leads to:

$STEPKEY = $webDriver->magentoCLI("helloworld")
 // stepKey: STEPKEY$webDriver->comment($STEPKEY)

[KevinBKozan]

Found a bug, see above.

Eventually @KevinBKozan fixed the bug.

[KevinBKozan]

No more bugs found, looks like this is good to go.