Add optional $params argument to query/execute adapter methods

[MasterOdin]

Closes #1954

This allows a new optional parameter to the query and execute adapter methods to allow you to pass in an array of parameters to be used in a prepared query on the underlying PDOAdapter. It's assume that custom adapters people may implement will also have some mechanism of utilizing a concept of prepared queries. To maintain backwards compatibility, if the optional parameter is empty, then we use the direct exec() and query() methods on the connection to maintain support for executing multiple queries in one go.

The aim here was to keep the return result for the two methods consistent with that's there, just adding the optional parameter. This is then also exposed upwards in the MigrationInterface and SeedInterface classes.

[MasterOdin]

This is marked as a draft as I've still got some amount of work to do to get this to work, and add tests across all adapters, but wanted input from @dereuromark, @garas, @Roy-Orbison that this would work for everyone's needs / expectations.

[Roy-Orbison]

This will cover most use cases.

All other problems/features I raised are voided by that fact that, when using the connection directly, one can call the startCommandTimer(), etc. methods themself. Exposing a wrapped connection or something to automate that timer would make the code unnecessarily complex.

[MasterOdin]

@dereuromark alright, finally returned to this and got it working, and should be ready for review, with fixed test case, and have also added to the docs for this.