PG to PG: TSTZRange and JSONB

[Amogh-Bharadwaj]

PG to PG CDC:

• Adds support for JSONB (now maps to JSONB on target)
• Constructs the string for tstzrange (still text on target) in a way that you can cast to tstzrange like select mytstzrange::tstzrange from table. This would fail before as the string we were inserting was of some json type string. Null lower and upper bounds tested

Functionally tested

[serprex]

What's the motivation for this? PG<>PG should use PG type system to have this accuracy & more. This direction with qvalue is pulled both towards being a common denominator format & a union of everything intersected with postgres. In this case it goes further, supporting distinctions which are only meaningful to postgres. At that point you might as well just be passing pgtype values around

Ideally range types would be generalized

[CLAassistant]

All committers have signed the CLA.

[serprex]

#1733 has merged, making this obsolete