WIP: Simplifying the step definitions

[noggan]

Goal is to simplify and make it clearer what steps should be used.

[noggan]

The questions I'm thinking about currently is:

• Typecasting parameters

Provide some way to specify the type of parameters given in TableNode. Some kind of suggestion is to automatically convert | [1,2,3] | to an array. Question is how we want to handle conversion to primitives (bool & int).

• Specifying default parameters for requests

As it is now, a user would need to provide the entire request body on each request. Perhaps it could be solved by adding a step like Given default body: which can be placed in a background or if the user needs to solve this themselves by cleverly using Scenario Outlines in behat. I would prefer not to specify this using options since those files grow pretty large already.

[noggan]

On another note there's no way we can deprecate all the existing steps before we properly rewrite the entity fixture context.