Add support for Oracle/PostgreSQL JSON validations

[nj1973]

Test case

Oracle:

CREATE TABLE dvt_test.tab_json
(
  id VARCHAR2(10) NOT NULL PRIMARY KEY
, col_json1 CLOB
, col_json2 CLOB
);
ALTER TABLE dvt_test.tab_json ADD CONSTRAINT tab_json_chk1 CHECK (col_json1 IS JSON) ENABLE;
ALTER TABLE dvt_test.tab_json ADD CONSTRAINT tab_json_chk2 CHECK (col_json2 IS JSON) ENABLE;
INSERT INTO dvt_test.tab_json VALUES (1,'{"a": 1}','{"a": 1}');
COMMIT;

PostgreSQL:

CREATE TABLE dvt_test.tab_json
(
  id varchar(10) NOT NULL PRIMARY KEY
, col_json1 json
, col_json2 jsonb
);
INSERT INTO dvt_test.tab_json VALUES (1,'{"a": 1}','{"a": 1}');

Oracle uses CLOB/NCLOB columns for JSON data, we should be able to compare these with PostgreSQL JSON columns. At a minimum, for column validation, we should be able to compare by string length like we do for some other string columns.

We need to check all validation types. Search for "issue-1338" in the repo.

We might need to revert some of the changes from #1335.

[nj1973]

We should add json/jsonb columns to the pso_data_validator.dvt_pg_types test table.