Question: Import xgboost as new port in vcpkg repo, build failed for arm64_osx, arm64_uwp, arm64_windows...

Hi xgboost community,

Recently I'm working on a c++ project that depends on xgboost. Because our project relies on [vcpkg](https://github.com/microsoft/vcpkg) for the library management, I'm trying to add xgboost to the vcpkg.
Here is my PR for import xgboost(v1.7.6) to vcpkg: https://github.com/microsoft/vcpkg/pull/38743
The changes were tested on windows64 and local build and tests passed.

**Issue**
some of GitHub Azure Pipeline build for the xgboost **failed**:
**arm64-osx, arm64_uwp, arm64_windows, arm_neon_android, x64_osx, x64_uwp, x86_windows.**
Others were **successful**:
**arm64_android, x64_android, x64_linux , x64_windows , x64_windows_static**
Full details of GitHub Azure Pipeline build failures: https://github.com/microsoft/vcpkg/pull/38743/checks?check_run_id=25252907894

**Question**
1. I'm wondering if builds failed because xgboost doesn't support those platform/OS? In that case I will exclude those builds for xgboost.
2. will xgboost support "arm64_windows"? Our project also builds for arm64_windows...

Start with the linked vcpkg PR and its Azure Pipeline check logs, especially the failures for arm64-osx, arm64_uwp, arm64_windows, arm_neon_android, x64_osx, x64_uwp, and x86_windows. Determine whether each failure reflects platform support or port configuration; done means documenting the support decision and applying the corresponding vcpkg change.

Written by the indexing model from the issue text.