Test jobs not completing on test-macstadium-macos11-arm64-2 with ChannelClosedException

Raising this to monitor it, in case it starts being a recurring problem.

Recent occurrences of test jobs failing with ChannelClosedException:

```
15:26:38 Cannot contact test-macstadium-macos11-arm64-2: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@4dfa7683:test-macstadium-macos11-arm64-2": Remote call on test-macstadium-macos11-arm64-2 failed. The channel is closing down or has closed down
...
15:35:34 wrapper script does not seem to be touching the log file in /Users/jenkins/workspace/Test_openjdk11_hs_extended.system_aarch64_mac@tmp/durable-bcf35e03
15:35:34 (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
```

To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:

- test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)? not specific to test suite
- a link into recent `Test_` job on https://ci.adoptium.net which showed the failure
- https://ci.adoptium.net/job/Test_openjdk11_hs_extended.system_aarch64_mac/111
- https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.openjdk_aarch64_mac/112/
- **Hyperlink** to re-run in Grinder:
- Is there an existing issue elsewhere covering this?
- Which machine(s) does it work on?
- Which machine(s) does it fail on? test-macstadium-macos11-arm64-2

Any other details:
Maybe this is a two-off failure from the recent [jdk11 2282 build pipeline](https://ci.adoptium.net/job/build-scripts/job/openjdk11-pipeline/2282/), will keep monitoring to see if it recurs:
https://trss.adoptium.net/searchResult?buildId=63fe453317052c6715e8d8ee&searchText=ChannelClosedException

Review the linked Test_openjdk11 jobs, the openjdk11 pipeline 2282, and the TRSS ChannelClosedException search result, focusing on test-macstadium-macos11-arm64-2 and the Jenkins log excerpts. Determine whether the failure recurs and document the affected jobs, machine scope, and confirmed cause or next infrastructure action.

Written by the indexing model from the issue text.