Clean up memory requirements for CI tests

[fhanik]

No description provided.

[fhanik]

First run - one job ([JUnit tests on database / container-test-job (postgresql-18)) failed. One test failed.

Note: the commit changes did not touch these tests.

[fhanik]

all passed. Spring Boot metaspace of 128MB is too small.

[duanemay]

Related to this as well, the comment in #3683
I was seeing the following message while running integration_test script locally.

The Daemon will expire after the build after running out of JVM Metaspace.
The project memory settings are likely not configured or are configured to an insufficient value.
The daemon will restart for the next build, which may increase subsequent build times.
These settings can be adjusted by setting 'org.gradle.jvmargs' in 'gradle.properties'.
The currently configured max heap space is '1 GiB' and the configured max metaspace is '128 MiB'.
For more information on how to set these values, please refer to https://docs.gradle.org/9.2.0/userguide/build_environment.html#sec:configuring_jvm_memory in the Gradle documentation.
To disable this warning, set 'org.gradle.daemon.performance.disable-logging=true'.

This gradle default is 384m, as shown in the doc:
https://docs.gradle.org/9.2.0/userguide/config_gradle.html#sec:configuring_jvm_memory