TASK: Remove doctrine migrate and cr setup commands from behat scripts

[mhsdesign]

Alternative fix to #5005 or the commits in #4988

When the ci is run without the doctrine schema setup the behat helper @flowEntities will create the schema.
This unfortunately messes with the transaction level as debugged:

array(2) {
  ["getTransactionNestingLevel"]=>
  int(119)
  ["isTransactionActive"]=>
  bool(true)
}

The working state - when the schema exists already - looks like this

array(2) {
  ["getTransactionNestingLevel"]=>
  int(0)
  ["isTransactionActive"]=>
  bool(false)
}

The CI complains with errors like

A transaction is active already, can't commit events!

or

Failed to acquire checkpoint lock for subscriber "Neos\ContentRepository\Core\Projection\ContentStream\ContentStreamProjection" because a transaction is active

But with neos/behat#40 we fix the problem and reset the transactions after the migration, so that we can remove the ci hack ./../flow doctrine:migrate.

Upgrade instructions

Review instructions

Checklist

• Code follows the PSR-2 coding style
• Tests have been created, run and adjusted as needed
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[mhsdesign]

Actually, due to this line in CI #5258 (comment) we now do doctrine:migrate at another place already so we wouldnt even need the adjustments of neos/behat#40 that are merged now.

But its good to have that hack cleaned up here from the composer scripts, so id say we can merge.