Fix Mapper::query() method to pass param types.

[andrejs]

When using custom query, it's not possible to use custom types for query parameters. For example:

$mapper->query(
    'SELECT * FROM user WHERE state IN (?)',
    [
        ['pending', 'active']
    ],
    [
        \Doctrine\DBAL\Connection::PARAM_STR_ARRAY
    ]
);

This pull request fixes the problem by passing custom param types to \Doctrine\DBAL\Connection::executeQuery() via Mapper::query().

[FlipEverything]

Off: The custom query above is just an example, right? Because you don't need to use a custom query for that. You can execute it like this: $mapper->where(['state IN' => ['pending', 'active']]);

On: I can't say anything about the usefullness of passing through the custom param type.

[andrejs]

Yes, it's just an example for the sake of simplicity. Intended usage of \Spot\Mapper::query() is for custom, complex queries, where you might also have typed parameters. Currently using query() you can't specify them, however it's supported directly by DBAL (see \Doctrine\DBAL\Connection::executeQuery). The method just doesn't proxy them. IMHO this is unnecessary limitation of Spot.

[FlipEverything]

I agree!

[tuupola]

Needs tests, otherwise looks good to me. Valitron bug was already fixed with #217.