add capture_sql method to compare sql statements and compare

Other methods compare specific patterns, this method outputs
the actual sql query that is generated.
add test to compare sql statements in delete_all query

delete_all sql if an association is not loaded should behave
the same as if the association is loaded. This test ensures
the SQL statements are exactly the same.
fix delete_all to remove records directly

When delete_all is run on a CollectionProxy and has a
dependency of delete_all the SQL that is produced has an IN
statement. (DELETE FROM `associated_model` where `associated_model`
.`parent_id` = 1 AND `associated_model`.`id` IN (1, 2, 3...)).
This only happens if the association is not loaded (both loaded
and non-loaded delete_all should behave the same. This is a huge
problem when it comes to deleting many records because the query
becomes very slow. Instead the SQL produced should be (DELETE FROM
`assoicated_model` where `associated_model`.`parent_model_id`=1).

I fixed this by making sure the check for loaded and destroy also
makes sure that the dependent is not delete_all, so the conditional
goes to the else and deletes the records directly without the IN
statement.
Merge pull request #14546 from eileencodes/fix_delete_all_to_not_use_IN_statement

Fix delete all to not produce sql in statement
refactor assert_sql query to reuse capture_sql

set assert_sql to reuse the capture_sql method from above
instead of repeating the code

in response to comments on issue #14546
Merge pull request #14548 from eileencodes/refactor_capture_sql_in_tests

refactor assert_sql query to reuse capture_sql
PostgreSQL determine `Column#type` through corresponding OID. #7814

I ran the whole test suite and compared the old to the new types.
Following is the list of types that did change with this patch:

```
DIFFERENT TYPE FOR mood: NEW: enum, BEFORE:
DIFFERENT TYPE FOR floatrange: NEW: floatrange, BEFORE: float
```

The `floatrange` is a custom type. The old type `float` was simply a coincidence
form the name `floatrange` and our type-guessing.
Merge pull request #14513 from senny/pg/responsible_oid

PostgreSQL determine `Column#type` through corresponding OID. #7814
PostgreSQL, register custom domains. Closes #14305.

This patch registers custom domains in our OID-type_map.
They will behave exactly as the type specified by `pg_type.typbasetype`.

/cc @matthewd
refactor, use `typtype` instead of `typinput` to segment PG types.