Demonstrates that NULL parameters are handled incorrectly by the sql parser utils as of 2.3.4

Fixed a PHP warning in DBALException::driverExceptionDuringQuery() when a parameter contains binary data.

- added test for getListTableColumnsSQL
- added test for getListTableForeignKeysSQL
- added test for getListTableIndexesSQL

This reverts commit d7032199.

DBAL-54 was fixed in commit 3d55dc8e by
changing SQL queries order. However it was later reintroduced.

This patch uses a different, more future-proof way, approach by using
DROP SEQUENCE ... CASCADE syntax, and thus does not depend on queries order.

fix :: operator in sql parser

[DBAL-374] Fix issue with column quoting in primary keys, fixing this in indexes in general is much more complex as the code is messy.

In some cases the Comparator class returns multiple drops for the same foreign key.
Specifically, in case you have two tables, A & B, with A having a foreign key FK
referencing B, if you drop table B, the resulting diff shows this FK twice,
once on the diff->orphanedForeignKeys array as we're deleting B, and another on
the diff->changedTables array as table A is also being modified. As a result of this you
get the DROP FOREIGN KEY instruction twice in the final SQL.

[DBAL-335] Fix nasty bug in MasterSlaveConnection, connecting and writing to slave when using keepSlave option.

Based on whether we are on 32 or 64 bit platform, postgres will return a string or an int for the expected php type of a bigint that is > 32 bits.

Use dropAndCreateDatabase schema manager function in test initialization instead of individual versions of each.