Spread 'Common' features to have a better BDD approach

### Spread 'Common' features to have a better BDD approach

Basically the Common features method that was adopted in earlier days, have many issues where there would be many hacks and tricks to make them work on all interfaces (API's and browser ones). There would be also scenarios which would only be possible to one or another that can't be covered by the common ones.
Also the BDD features should act (somehow) as documentation, which couldn't be accomplished with common features.

----

Todo's:
- [x] Correct sentences and remove deprecated
- [x] Remove all the common features
- [x] Add sentences/methods for those scenarios that couldn't be covered before
- [x] Add data mapping (for the id manipulation, which can't be defined through BDD)
- [x] Add verification of ContentTypeGroup existence through Public API
- [ ] waiting for the ezsystems/BehatBundle#1 to be merged

----

Needs:
- ezsystems/ezpublish-kernel#889
Since this "common" feature grouping wont exist, I've moved the `$pageIdentifierMap` to the `BrowserContext` since for REST we will use the resource url's (withouth the `/api/ezp/v2/`) and for Public API there isn't pages (url's) involved