Align AArch64 ACL integration with oneDNN v3.10.x

[allnes]

Summary

This PR aligns the OpenVINO oneDNN fork delta for AArch64 ACL support with the v3.10.x integration branch.

The change makes the ACL integration explicitly AArch64-only, moves the ACL-backed CPU primitive code into the AArch64 CPU implementation area, and updates the build and primitive registration paths to use the AArch64-specific ACL configuration.

Technical details

• Replaces the generic DNNL_USE_ACL build option with DNNL_AARCH64_USE_ACL.
• Removes the 32-bit ARM target path from the forked oneDNN CPU architecture selection.
• Moves ACL-backed primitive sources from src/cpu/acl into src/cpu/aarch64 and updates namespaces, includes, and CMake source selection accordingly.
• Registers ACL implementations through AArch64-specific guards, including the ACL reorder implementation used by OpenVINO CPU plugin layout conversions.
• Updates AArch64 CPU primitive lists, ACL threading integration, platform flag handling, and JIT profiling defaults to match the AArch64-only ACL model.
• Updates AArch64 build and CI workflow definitions to use the new option name and target architecture contract.
• Removes AArch64 CI matrix entries that target unavailable c6g/c7g/c8g runner labels and keeps the affected jobs on available MacOS/cb100 runner paths.
• Enables ccache for AArch64 ACL cache builds and oneDNN CMake builds, including PR, nightly, and performance workflow paths.
• Excludes currently unsupported/failing Linux AArch64 graph tests from the cb100 CI pass through the existing skipped-test filter.

Scope

The PR is intended to provide the oneDNN-side dependency revision consumed by OpenVINO through src/plugins/intel_cpu/thirdparty/onednn. It does not require OpenVINO to use an external oneDNN source tree.

openvinotoolkit/openvino#36193

[dzarukin]

Unrelated to PR question: wouldn't it be cheaper to migrate to v3.12 instead of cherry-picking all those necessary changes?

[allnes]

Unrelated to PR question: wouldn't it be cheaper to migrate to v3.12 instead of cherry-picking all those necessary changes?

@dzarukin Migrating to v3.12 would mean moving the whole oneDNN dependency to v3.12 across all supported architectures, not just taking the AArch64 pieces. That is a much broader integration and validation effort. This PR is intentionally narrower: it removes the obsolete 32-bit ARM path and aligns the AArch64/ACL fork delta with the UXL oneDNN version currently used for this OpenVINO integration.