drop domain support

[jennifersp]

Added:

• merge functionality for domain types
• check for domain usage in tables for dropping domain

TODO:

• creating domain type creates instance of array type of this domain type
• unique OID generated for each domain created
• add domains to pg_type
• ALTER TABLE (e.g.: modify existing column to domain type column)
• use domain type as underlying type to another domain

[github-actions[bot]]

	Main	PR
Total	42090	42090
Successful	12845	12864
Failures	29245	29226
Partial Successes[^1]	4896	4892

	Main	PR
Successful	30.5179%	30.5631%
Failures	69.4821%	69.4369%

${\color{lightgreen}Progressions}$

constraints

QUERY: DROP DOMAIN constraint_comments_dom;

domain

QUERY: drop domain domainvarchar restrict;

QUERY: drop domain domainnumeric restrict;

QUERY: drop domain domainint4 restrict;

QUERY: drop domain domaintext;

QUERY: drop domain domainint4arr restrict;

QUERY: drop domain dia;

QUERY: drop domain dnotnull restrict;

QUERY: drop domain dnull restrict;

QUERY: drop domain dcheck restrict;

QUERY: drop domain ddef1 restrict;

QUERY: drop domain ddef2 restrict;

QUERY: drop domain ddef3 restrict;

QUERY: drop domain ddef4 restrict;

QUERY: drop domain di;

QUERY: drop domain testdomain1;

drop_if_exists

QUERY: DROP DOMAIN IF EXISTS test_domain_exists;

QUERY: DROP DOMAIN IF EXISTS test_domain_exists;

QUERY: DROP DOMAIN IF EXISTS no_such_schema.foo;

json

QUERY: DROP DOMAIN js_int_not_null;

jsonb

QUERY: DROP DOMAIN jsb_int_not_null;

security_label

QUERY: DROP DOMAIN seclabel_domain;

[^1]: These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct.