This reverts commit e3ab1276, reversing
changes made to f988b0a6.

The reasoning behind this is to essentially rely on a single type (or
the absence of it), therefore add type declarations.

Since these are private methods we can do that without breaking BC.

fixes #1339
closes #921

Take the column order into account and sort non PK columns last

- Fixed docblocks
- Removed return statements on void methods
- Cleaned up unused private / local variables
- Fixed license issues
- Removed SVN leftovers
- Fixed doctrine-project.org links
- Added line breaks before return statements

These are internal, automatically-created and shouldn't be considered part of
the schema. They cannot be recreated because of their reserved names.

* The old implementation produced invalid SQLite statements for tables with
  a composite primary key, as SQLite cannot have more than one primary key
  clause and autoincrement can only be declared on a single column
* There is currently no way to tell from its pragma if an SQLite column
  auto-increments, therefore enabling it on all primary keys is not accurate
* SQLite primary keys auto-increment anyway (but slightly differently from an
  actual auto-increment column -- not guaranteed unique)

Fixed a problem in PostgreSql AutoIncrement Detection, changed Autoincrement API for platform/schema manager interaction a little bit