Run JDBC tests in Testcontainers (MVP)

[ostinru]

Add testcontainers-bassed automation tests

For new tests I used testcontainers. This is a shift in the way we running automation tests:

• new tests run on host machine (you can run tests from your IDE)

  +----------------------------------------------------------------+
  |                              Host                              |
  |  +-------------------------------+  +-----------------------+  |
  |  |           Docker              |  |        Docker         |  |
  |  |   [Cloudberry] --> [PXF] ------------>  [Database]       |  |
  |  |                               |  |                       |  |
  |  +-------------------------------+  +-----------------------+  |
  |                                                                |
  |                         [Automation]                           |
  +----------------------------------------------------------------+
  

• new test framework manages Docker containers on its own:
  • it will start only required containers
  • all test-specific code is located near test (not in a single bash-file)
  • it opens a way to run highly custom containers (kerberos tests?)
• No jSystemCore. This framework have not active development for couple years. New classes uses same TestObject pattern, but have no direct dependency on jSystemCore.

Containers

New framework uses shrinked version of pxf-cbdb-dev:

• no hadoop ecosystem in the same container
• no more file permission issues - we copy files to container instead of mapping (binding) them in RW mode
• faster cloudberry + PXF builds:
  • no pxf-cli - it is unused
  • gradle is baked into docker image - no downloads during container run
  • map system-wide gradle cache to container as RO cache

[ostinru]

This is minimal version of #84 (which is stuck on issues with ClickHouse). Difference:

1. No Clickhouse tests (they are broken)
2. Add Rocky Linux 9 support

[MisterRaindrop]

LGTM

[ostinru]

For some reason bunch of Parquet* tests failed on Rocky Linux. I don't think that one jdbc test can lead these tests failure.