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.
Indeed.. It's a pain that it's the first parameter. However, this is a parameter that really has no right to be here, let alone the first parameter. 

For long-term benefits we may have to take short term pains.. I'd be in favour of a removal. *at least* throwing a deprecation warning and then taking it out of 3.3?

As @hafriedlander has said, the point of SS 3 was to make breaking changes to APIs that could be improved