Add support for Orka

[smlambert]

Fixes #4899

Update PLATFORM_MAP with Orka dynamic agent for Mac platforms

[smlambert]

Grinder on aarch64_mac: https://ci.adoptium.net/view/Test_grinder/job/Grinder/8139/

[smlambert]

Grinder running extended.openjdk in PARALLEL=Dynamic across 5 machines x86-64_mac:
https://ci.adoptium.net/view/Test_grinder/job/Grinder/8140

• takes up the 2 static macincloud machines, leaving none idle
• Grinder running on x86-64_mac while all static machines idle: https://ci.adoptium.net/view/Test_grinder/job/Grinder/8141/

[sophia-guo]

This PR is eventually needed.

However this might not be the fix for #4899. See my comment in #4899

I run a grinder with master which still works for mac aarch64 as in grinder the ACTIVE_NODE_TIMEOUT will be set as 15 min.
https://ci.adoptium.net/view/Test_grinder/job/Grinder/8154/console

[sophia-guo]

Also feels like this orka's configuration is different from azure linux dynamic agent ones. Azure dynamic ones works like if there is no available agent then we add label &&ci.agent.dynamic, and dynamic agent will be generated. This orka one is if label [ci.role.test&&hw.arch.aarch64&&(sw.os.osx||sw.os.mac)](https://ci.adoptium.net/label/ci.role.test&&hw.arch.aarch64&&%28sw.os.osx%7C%7Csw.os.mac%29) agent not available it will be generated with label ci.role.test&&hw.arch.aarch64&&(sw.os.osx||sw.os.mac), that means no label 'ci.agent.dynamic'. Can't see the configuration and not sure if it's the final configuration. Depends on that logic on aqa-tests need to update correspondingly.

[sophia-guo]

In short the orka test agent is used in a different way from the current dynamic agents logic is aqa-tests.

[smlambert]

@sophia-guo - by your comment, do you feel this PR, adoptium/ci-jenkins-pipelines#853 is a preferred approach? If so, I can close this one and move that one out of draft.

[karianna]

Ugh sorry, pulled the trigger too fast - reversal PR #4913