[CI] Build NCHWc code on Windows/Linux ARM64 CIs (microsoft#27273)

### Description

Initially the NCHWc code was built only on Mac CIs to keep the build
path regression-free.

There were some Linux-specific paths introduced in
microsoft#26838 and there is more
community interest in contributing to these code paths. See
microsoft#27099. Hence, it makes
sense to keep these code paths built and tested on Linux and Windows
too.

### Motivation and Context
Improve CI quality with regards to ARM64 NCHWc builds

CC: @Rohanjames1997

Author: hariharans29

.github/workflows/linux_ci.yml

@@ -94,7 +94,7 @@ jobs:
       dockerfile_path: tools/ci_build/github/linux/docker/inference/aarch64/default/cpu/Dockerfile
       docker_image_repo: onnxruntimecpubuildciaarch64
       # ASan disabled due to excessive runtime (>4hr). Includes wheel build for basic checks.
-      extra_build_flags: '--use_binskim_compliant_compile_flags --build_shared_lib'
+      extra_build_flags: '--use_binskim_compliant_compile_flags --build_shared_lib --enable_arm_neon_nchwc'
       job_identifier: build-linux-arm64-debug
     secrets:
       GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

tools/ci_build/github/azure-pipelines/win-qnn-arm64-ci-pipeline.yml

@@ -53,7 +53,11 @@ jobs:
     matrix:
       SHARED_LIB:
         QnnLibKind: 'shared_lib'
-        ExtraQnnBuildArgs: '--client_package_build'
+        # We currently do not have a standalone Windows ARM64 CI pipeline for the CPU EP,
+        # so we enable --enable_arm_neon_nchwc for additional coverage of the NCHWc code paths in the CPU EP.
+        # Once we have a standalone Windows ARM64 CI pipeline for the CPU EP, we can consider adding --enable_arm_neon_nchwc
+        # to that pipeline and removing it from this pipeline since this pipeline is primarily for testing the QNN EP.
+        ExtraQnnBuildArgs: '--client_package_build --enable_arm_neon_nchwc'
       STATIC_LIB:
         QnnLibKind: 'static_lib'
         ExtraQnnBuildArgs: ''