[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.
What do you mean with "CI configuration that has more than 1 DB" ?
It can not be parallelism, that would better be served by setting them up as separate jobs.

Could you instead mention the original use case instead of your feature description? (this feature description does not reflect our users needs btw, features should center on users, not a CI tool)