fix: EXPOSED-501 Column.transform() ignores custom setParameter() logic

[bog-walk]

Description

Summary of the change:
Adds an override for setParameter() to ColumnWithTransform class.

Detailed description:

• Why:

Any column type that relies on logic in setParameter() to succeed when preparing a statement will fail if transform() is used to convert it to ColumnWithTransform. This happens because the delegate's implementation is being ignored by the wrapping class.

This behavior can be seen if a custom column type is created that relies on some conversion in setParameter(); for example, needing to use PGobject when setting the parameter type with PostgreSQL.
Or, as shown in the test, using json().transform().

The same operations that succeed with a standard json() will fail with json().transform(), throwing something like:

org.postgresql.util.PSQLException: ERROR: column "numbers" is of type json but expression is of type character varying
  Hint: You will need to rewrite or cast the expression.

This would also fail on H2 because encodeToByteArray() is not being reached inside setParameter().

• How:

Adding ColumnWithTransform.setParameter() that uses delegate's function ensures that it is invoked.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix

Affected databases:

• All

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs

---

Related Issues

EXPOSED-501