API New Parameterised Database ORM for Silverstripe 3.2. Ticket #7429

* Database abstraction broken up into controller, connector, query builder, and schema manager, each independently configurable via YAML / Injector
* Creation of new DBQueryGenerator for database specific generation of SQL
* Support for parameterised queries, move of code base to use these over escaped conditions
* Refactor of SQLQuery into separate query classes for each of INSERT UPDATE DELETE and SELECT
* Support for PDO
* Installation process upgraded to use new ORM

See:
* http://open.silverstripe.org/ticket/7429 for ticket
* https://groups.google.com/forum/?fromgroups=#!topic/silverstripe-dev/jLk3bgeCebI For discussion around the changes involved
* https://github.com/silverstripe/silverstripe-cms/pull/311 CMS pull request

Everything is going to break all at once and I'm anticipating lots of hard work in the near future.

Pull requests for DB connector modules with upgraded code to follow.
Since this is also set in the default YAML, perhaps that should be updated instead? I can see people getting confused if they change one place later and it doesn't update (really only matters for non-CMS controlled routes)