The `PostgreSqlPlatform`, `SQLAnywherePlatform` and `SQLServerPlatform` classes have been renamed to `PostgreSQL94Platform`, `SQLAnywhere16Platform` and `SQLServer2012Platform` respectively.

When deprecating an old platform version, we can deprecate and later remove a specific class. Otherwise, there's no way to express the deprecation on the class level and the upgrade notes contain sentences like: "`XYZPlatform` and `XYZKeywords` now represent XYZ (version)".

It was not covered, probably because it was hard to do something
generic. I choose to duplicate some tests instead, so that things stay
relatively simple.

Minor code cleanup for efficiency, and tests to check the order by clause scrubbing is working correctly and not entering an infinite loop

Fix more occurances of the extending Test bug, "reactivating" a total of 200 tests. SQLAnywhere is missing and is a bit more annyoing to fix, because of a deep inheritance hierachy.

Apperently the doModifyLimitQuery function does not only cover SQL
generated by ORM (Makes sense to use DBAL as seperate component). Therefor
it can happen that a column name does not include the table and so the old
logic was valid anyway. (line 867-869)

Fixed the unit tests to use real column names instead of aliases.

and takes inspiration from this PR https://github.com/doctrine/dbal/pull/374 which was written for this bug http://www.doctrine-project.org/jira/browse/DDC-2622

[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.