Separate collection inputfilter validation

[tigran-m-dev]

Added new functionality to allow create separate validation inputfilters if we have REST API. For example if we have update (PUT) and updateList (PUT collection). Before this changes we can't specify different validation for update and updateList because they are both PUT request, but now it is possible to just specify key PUT and PUT_COLLECTION

[coveralls]

Coverage decreased (-2.3%) to 78.431% when pulling 80b84fa on developer-devPHP:separate_collection_inputfilter_validation into afa233a on zfcampus:master.

[michalbundyra]

@developer-devPHP We need tests for those changes.

[tigran-m-dev]

@webimpress
I just pasted example that you have in your doc and changed using this new functionality, which is under PUT_COLLECTION.
In this example we are using Update and Collection Update (List update)
And for each of methods we could specify different Validator

'zf-content-validation' => [
    'Application\Controller\HelloWorld' => [
        'input_filter' => 'Application\Controller\HelloWorld\Validator',
        'PUT' => 'Application\Controller\HelloWorld\UpdateValidator',
        'PUT_COLLECTION' => 'Application\Controller\HelloWorld\UpdateCollectionValidator',
    ],
],

[tigran-m-dev]

@webimpress and @weierophinney
I added test for this new functionality. When you have a time please check and let me know your thoughts.
Thanks.

[weierophinney]

Thanks, @developer-devPHP; merged to develop for release with 1.5.0.