Fix the pipeline breaks dues to the MSVC 19.40 and numpy 2.0 release

[wenbingl]

inspired by this PR: microsoft/onnxruntime#21004

[wenbingl]

@snnn any idea why the following command line doesn't work

2024-06-14T23:22:52.1858496Z "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -S D:\a_work\1\s -B .scb\temp.win-amd64-cpython-312\Release -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=D:\a_work\1\s.scb\lib.win-amd64-cpython-312\onnxruntime_extensions -DOCOS_ENABLE_CTEST=OFF -DOCOS_BUILD_PYTHON=ON -DOCOS_PYTHON_MODULE_PATH=D:\a_work\1\s.scb\lib.win-amd64-cpython-312\onnxruntime_extensions_extensions_pydll.cp312-win_amd64.pyd -DCMAKE_BUILD_TYPE=Release -DOCOS_USE_CUDA=ON "-T cuda=D:\a_work_temp\v11.8" -DCMAKE_CUDA_FLAGS_INIT=--allow-unsupported-compiler -DCMAKE_CUDA_ARCHITECTURES=70;86

[snnn]

Use the latest cmake

[snnn]

Remove "python -m pip install cmake"

[snnn]

The machine already has cmake

[snnn]

Do not use C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe
Use

 C:\Program Files\CMake\bin\cmake.exe

[snnn]

I deleted one of the cmake from the VM image. Then one of the failed pipelines passed.

[wenbingl]

I deleted one of the cmake from the VM image. Then one of the failed pipelines passed.

Why is there no C:\program files\cmake... in CUDA Windows machine?

[snnn]

I deleted one of the cmake from the VM image. Then one of the failed pipelines passed.

Why is there no C:\program files\cmake... in CUDA Windows machine?

It shouldn't. Could you give me a link of the log?

[wenbingl]

I deleted one of the cmake from the VM image. Then one of the failed pipelines passed.

Why is there no C:\program files\cmake... in CUDA Windows machine?

It shouldn't. Could you give me a link of the log?

There is no direct log. Python code detected ProgramFiles/CMake firstly then falled back to VS/cmake. In this log, https://dev.azure.com/onnxruntime/onnxruntime/_build/results?buildId=1409852&view=logs&j=1130dc32-b83a-5b28-25cb-8e5ca42e48d6&t=524fdcc1-2f40-5737-3487-03bf6009139b, it did fallback to vs/cmake.