Behat testing Modular or not Modular

We need to decide if the Behat (functional/browser) tests should be in each bundle or be in a separate distribution especailly dedicated to developing Sulu, a Sulu Developer edition.

Having modular browser tests. But this presents some problems:

• Bootstrapping the kernel.
• Installing the bower dependencies into the bootstrapped folder
• Running the server for debugging (related to bootstrapping)

Whilst having a develop edition has some benefits:

• It is tested in the way that Sulu is used (i.e. in a distribution)
• It is easy to setup a vhost for it
• We decouple the longer running browser tests from the shorter integration / unit tests
• The build could be triggered from another Travis job (i.e. when the sulu/sulu test suite finishes)
• Such a distribution could also serve as the platform for PR testing.