test: performance workflow improvements DHIS2-20175

[teleivo]

• We used basic auth in our performance tests so far. This meant hashing showed up in our CPU profiles as we did that on every request. That is not how users should interact with our API though. Capture will login and use a cookie with the sessionid. Use the approach like in AuthenticationControllerTest and let Gatling handle the JSESSIONID cookie. Gatling detects Set-Cookie headers automatically in the response to login.
• Allow running specific performance tests via git tag in GitHub workflow using arg perf_tests_git_ref
• Allow profiling in GitHub workflow using arg prof_args
• Add hard CPU limits to performance test containers so db and web containers are more isolated
• Fix log4j2.xml configuration for performance tests as I accidentally committed it as a directory 🤦🏻
• Use more up to date PostgreSQL version https://www.postgresql.org/support/versioning
• Fix postgres.conf location as it was not in the default location (and not configured to look elsewhere)
• Fix typo in dhis-2/dhis-test-performance/docker/dhis.conf
• Simplify container startup wait logic using docker compose --wait
• Remove Docker pull warnings by using image: localhost/... for the DB image. The DB image is purely a local image
• Use bao image for ARM architecture support like we do in core to fix test: allow profiling performance tests DHIS2-20175 #22080 (comment)
• Describe the purpose of Dockerfile.postgres which for now is just caching the DB dump
• Pull mutable Docker images like dhis2/core-dev:master, dhis2/core-dev:latest, dhis2/core-pr:<pr number> so they are up to date. This is necessary as our self-hosted runner is not ephemeral so images are cached
• Add DHIS2 Docker image labels we add to our images like DHIS2_BUILD_REVISION to the job summary. This is especially important for all the mutable images
• Add a command to re-run the workflow with the same parameters to a job summary

Sample run

Tested these changes with

gh workflow run run-performance-tests.yml \
        --field perf_tests_git_ref="DHIS2-20175" \
        --field simulation_class="org.hisp.dhis.test.tracker.TrackerTest" \
        --field prof_args="-e cpu" \
        --field dhis2_image_baseline="dhis2/core:2.42.2" \
        --field dhis2_image_candidate="dhis2/core-dev:master" \
        --field dhis2_db_dump_url="https://databases.dhis2.org/sierra-leone/2.42.2/dhis2-db-sierra-leone.sql.gz" \
        --field dhis2_db_image_suffix="sierra-leone-2.42.2" \
        --ref DHIS2-20175

results are in https://github.com/dhis2/dhis2-core/actions/runs/18185378283

Gatling references on auth

• https://docs.gatling.io/reference/script/protocols/http/helpers/
• https://docs.gatling.io/guides/use-cases/basic-auth/
• https://gatling.io/blog/gatling-credentials
• https://community.gatling.io/t/is-set-cookie-saved-automatically-by-gatling-session/8042

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud