Fixed inconsistent use of getSQLDeclaration method

Fixed inconsistent use of getSQLDeclaration method

Fixed inconsistent use of getSQLDeclaration method

Fixed inconsistent use of getSqlDeclaration method name

Because PostgreSQL will return the expression with a lot of
parentheses we cannot TRIM() them easily. It is easier and more
correct to adapt to what PostgreSQL returns. That means the declaration
of partial indexes must be updated as follow:

Before:
``options={"where": "other_id IS NULL"}``

After:
``options={"where": "(other_id IS NULL)"}``

And fore more complex conditions, that would be:
``options={"where": "(((id IS NOT NULL) AND (other_id IS NULL)) AND (name IS NULL))"}``

Simplified doModifyLimitQuery per @deeky666 comments, added test case for orderby with parenthetical expression

Added doModifyLimitQuery for SQLServer2012Platform that uses OFFSET... FETCH instead of the awful SQL Server 2008 window function garbage

These objects are created by turning on replication and they have column types (sysname, xml) that are not supported by Doctrine. 

According to Microsoft's support, these are "'pseudo-system' object[s]" that appear in the User Table type instead of the System Table type.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/135ec547-2214-4da3-bd42-5c458759e144/sysobjectscategory