[codex] install Allure and preserve test entrypoints

[kycheng]

What changed

• install Allure CLI 2.32.0 and its headless JRE in the E2E test image
• validate the Allure installation during the image build
• use /app/bin/sonarqube-e2e.test as the image entrypoint
• preserve /app/testing/sonarqube-e2e.test as a compatibility symlink

Why

The release-test workflow generates Allure results and then renders an HTML report inside the test image, but the current image does not contain the Allure CLI. The image also copies the test binary to /app/bin while its entrypoint points at the non-existent /app/testing path.

The Allure installation follows the approach validated in AlaudaDevops/tektoncd-pipeline#289. Keeping both test-binary paths avoids breaking existing consumers while the canonical entrypoint moves to /app/bin.

Validation

• git diff --check
• built the change as an additional layer on the current amd64 SonarQube test image
• verified allure --version resolves to 2.32.0
• verified both /app/bin/sonarqube-e2e.test and the compatibility path /app/testing/sonarqube-e2e.test are executable and resolve to the same binary
• verified the image entrypoint is /app/bin/sonarqube-e2e.test

The full build from build-harbor.alauda.cn/devops/sonarqube-ce-test-base:latest is currently blocked because that base image references a missing remote layer blob. The changed runtime layer itself was validated against the latest locally available SonarQube test image.