Ensures that Postgresql works with blob types bytea and oid (large objects)

[filipelautert]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Postgresql defines 2 column types to handle blob types: bytea and large objects that must be declared as "oid". According to postgresql documentation, both must use different jdbc methods (https://jdbc.postgresql.org/documentation/binary-data/) .

Until Liquibase 4.13, bytea was supported. But #605 changed the methods to support large objects instead of bytea.

This fix validates the column type and uses the appropriated jdbc method depending on it.

Things to be aware of

• A column cache has been created to make sure that snapshot data for a column is requested only once
• After this patch, both oid and bytea column types should work.

Things to worry about

• NA

Additional Context

• Fixes Problem inserting valueBlobFile into bytea column postgres #3165

[github-actions]

Unit Test Results

  4 668 files  ±  0    4 668 suites  ±0   33m 46s ⏱️ -42s
  4 642 tests +  1    4 416 ✔️ +1     226 💤 ±  0  0 ❌ ±0 
54 708 runs  +12  49 634 ✔️ +1  5 074 💤 +11  0 ❌ ±0 

Results for commit e01a198. ± Comparison against base commit ea43d36.

♻️ This comment has been updated with latest results.

[nvoxland]

Changes make sense, and adds integration tests

[XDelphiGrl]

Liquibase 4.12 introduced a regression in handling Postgres blob types. This regression caused inserts of data into Postgres columns of datatype of bytea to fail due to Liquibase treating the data as a large object (oid). Liquibase now supports Posgres bytea and Postgres oid blob types.

• New integration tests added.
• No additional testing necessary.

APPROVED