Rectify GHA CI workflow for s390x

[yasiribmcon]

Summary

1. Why: Currently GHA CI builds for s390x are failing consistently, blocking the CI workflow.
2. What: Added correct way of running multiple instructions during docker run command, updated temurin image to 11-jdk so that it can be in sync with ubuntu-latest image and introduced continue-on-error due to intermittent test case failures on temurin container.

Expected Behavior

gradle build command should run inside the s390x emulated temurin container and should pass.

Actual Behavior

gradle command actually runs on ubuntu-latest(which is x86_64) image which may or may not fail based on ubuntu-latest's jdk version which keeps on updating.

Steps to Reproduce

1. Check GHA CI build log for s390x

Known Workarounds

No

Additional evidence

1. This issue is similar to Re-enable s390x build for CI #2209 which is happening on CircleCI instead of GHA, where we discussed that the gradle build command is actually running on x86_64 instead of s390x. But since this build takes 2.5+ hours to complete in CircleCI, i could not do the same as I got build timeout from CircleCI.
2. Test cases are failing intermittently inside temurin container due to which i had to introduce continue-on-error flag, this would free up the GHA CI workflow.
3. Build run with all test passing : https://github.com/yasiribmcon/cruise-control/actions/runs/13069196316/job/36466943768
4. Build run with intermittent tests failing : https://github.com/yasiribmcon/cruise-control/actions/runs/13069196316

Categorization

• documentation
• bugfix
• new feature
• refactor
• security/CVE
• other

This PR resolves #2209

[CCisGG]

Thanks @yasiribmcon !