ZipException observed on some s390x nodes

An interesting test case failure that only happens on certain s390x machines (see: https://github.com/adoptium/aqa-tests/issues/4256#issuecomment-1396282406).

https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.openjdk_s390x_linux_testList_2/76 - has 10 testcases failing with java.util.zip.ZipException: invalid entry compressed size (expected 2287 but got 2286 bytes)

[jdk_security3_1](https://trss.adoptium.net/output/test?id=63c8879ded0b30773bb86bc4) => [deep history 4/11 passed](https://trss.adoptium.net/deepHistory?testId=63c8879ded0b30773bb86bc4) | [possible issues](https://trss.adoptium.net/possibleIssues?buildId=63c886a6ed0b30773bb86762&buildName=Test_openjdk11_hs_extended.openjdk_s390x_linux_testList_2&testId=63c8879ded0b30773bb86bc4&testName=jdk_security3_1) - these are unknown cause ZipException invalid entry compressed size (expected 2287 but got 2286 bytes) failures - but also try running on test-marist-ubuntu2004-s390x-1 [Grinder/6445](https://ci.adoptopenjdk.net/job/Grinder/6445) since it passed on that machine on Nov 12th (as shown in Deep History) - pass

This issue may be transferred to infrastructure repo, after initial triage.

Start with the linked CI job and TRSS deep history for jdk_security3_1, then compare the failing s390x node with the passing test-marist-ubuntu2004-s390x-1 run from Grinder/6445. Determine whether the ZipException is reproducible on a specific machine or belongs in the infrastructure repository; done means the cause and repository ownership are identified.

Written by the indexing model from the issue text.