TASK: Unify command and event dispatching in Behat tests

[bwaidelich]

While working on tests for the ContentRepository privileges I realized a couple of inconsistencies with our test suite.
For example:

When the command <SomeCommand> is executed with payload:

behaves differently from

When the command "<SomeCommand>" is executed with payload:

because they map to different step implementations.

Furthermore there was a huge amount of duplication and it wasn't easily possible to emit commands from a different source (i.e. from Scenario Outlines)

With this change, command handling is centralized to the GenericCommandExecutionAndEventPublication trait and it will allow for writing tests like

  Scenario Outline:
    When the command <command> is executed with payload '<command payload>' and exceptions are caught
    Then the last command should have thrown an exception of type "SomeException" with code 1729086686

    Examples:
      | command             | command payload                                                                              |
      | EnableNodeAggregate | {"workspaceName":"live","nodeAggregateId":"a1","nodeVariantSelectionStrategy":"allVariants"} |

[kdambekalns]

👍 by 👀

[mhsdesign]

Wow thanks that was probably a lot of effort :D

[mhsdesign]

this is just temporary as we think of making this nullable or introducing and actual Default here. https://github.com/neos/neos-development-collection/pull/5314/files#diff-4a3a69f0f68fa88f95e6a757f42dee32aa9a14a34ed99433e09a6950b5be0ce1