[TEST] Add paths to profiles to ease features select

Since the change of the [grouped features to spread ones](https://github.com/ezsystems/ezpublish-kernel/pull/889) that the feature files will be all under the same root, 

so instead of having few tags spread all over the features to select the exact ones, we can simplify with paths on the behat.yml and have a simple approach to the feature files.

PS:
the setup wizard feature might look more complicated than before but really it have more tags do identify the seveal possibilities, contemplating the future testing of the SW where it will test all installations in the same suite.
In travis, we have two databases. But if some other user runs the tests, he might only have one db in his system, so one of the setup wizard steps will be skipped. 
On BDD, we have two options:
- Either we assume that we only have one database (or two);
- or we have two scenarios (1 Db ; more than 1 db), whose conditional execution will be controlled by tags