GH-45041: [Packaging][Python] Use ORC from vcpkg instead of bundled on Linux and macOS

[raulcd]

Rationale for this change

We are currently downloading and building ORC every time for our wheels. We should not require to bundle ORC ourselves and we could just use vcpkg.

What changes are included in this PR?

Stop using ORC_SOURCE=BUNDLED and enable the vcpkg orc feature.

Are these changes tested?

Yes, on the wheels.

Are there any user-facing changes?

No

• GitHub Issue: [CI][Packaging][Python] wheel builds compile a bundled ORC #45041

[raulcd]

@github-actions crossbow submit wheel-manylinux-2-28-cp312-cp312-amd64

[github-actions]

Revision: 6eb5042

Submitted crossbow builds: ursacomputing/crossbow @ actions-b309acbcb8

Task	Status
wheel-manylinux-2-28-cp312-cp312-amd64

[raulcd]

We can see on the new logs, and is not downloaded/built anymore:

 -- Found orcAlt: /opt/vcpkg/installed/amd64-linux-static-release/lib/liborc.a (found version "2.0.0")
-- Providing CMake module for FindorcAlt as part of Arrow CMake package
-- Found ORC static library: /opt/vcpkg/installed/amd64-linux-static-release/lib/liborc.a
-- Found ORC headers: /opt/vcpkg/installed/amd64-linux-static-release/include

the orc tests on pyarrow being successful:

usr/local/lib/python3.12/site-packages/pyarrow/tests/test_orc.py ....... [ 86%]
......                                                                   [ 87%]

Previously it was built and we could see both the build process and the following log:

 -- Building Apache ORC from source

[raulcd]

@github-actions crossbow submit wheel-manylinux-*

[github-actions]

Revision: 6eb5042

Submitted crossbow builds: ursacomputing/crossbow @ actions-a95168b3c6

Task	Status
wheel-manylinux-2-28-cp310-cp310-amd64
wheel-manylinux-2-28-cp310-cp310-arm64
wheel-manylinux-2-28-cp311-cp311-amd64
wheel-manylinux-2-28-cp311-cp311-arm64
wheel-manylinux-2-28-cp312-cp312-amd64
wheel-manylinux-2-28-cp312-cp312-arm64
wheel-manylinux-2-28-cp313-cp313-amd64
wheel-manylinux-2-28-cp313-cp313-arm64
wheel-manylinux-2-28-cp313-cp313t-amd64
wheel-manylinux-2-28-cp313-cp313t-arm64
wheel-manylinux-2-28-cp39-cp39-amd64
wheel-manylinux-2-28-cp39-cp39-arm64
wheel-manylinux-2014-cp310-cp310-amd64
wheel-manylinux-2014-cp310-cp310-arm64
wheel-manylinux-2014-cp311-cp311-amd64
wheel-manylinux-2014-cp311-cp311-arm64
wheel-manylinux-2014-cp312-cp312-amd64
wheel-manylinux-2014-cp312-cp312-arm64
wheel-manylinux-2014-cp313-cp313-amd64
wheel-manylinux-2014-cp313-cp313-arm64
wheel-manylinux-2014-cp313-cp313t-amd64
wheel-manylinux-2014-cp313-cp313t-arm64
wheel-manylinux-2014-cp39-cp39-amd64
wheel-manylinux-2014-cp39-cp39-arm64

[raulcd]

@github-actions crossbow submit wheel-macos-*

[github-actions]

Revision: 6eb5042

Submitted crossbow builds: ursacomputing/crossbow @ actions-ad62b7a323

Task	Status
wheel-macos-monterey-cp310-cp310-amd64
wheel-macos-monterey-cp310-cp310-arm64
wheel-macos-monterey-cp311-cp311-amd64
wheel-macos-monterey-cp311-cp311-arm64
wheel-macos-monterey-cp312-cp312-amd64
wheel-macos-monterey-cp312-cp312-arm64
wheel-macos-monterey-cp313-cp313-amd64
wheel-macos-monterey-cp313-cp313-arm64
wheel-macos-monterey-cp313-cp313t-amd64
wheel-macos-monterey-cp313-cp313t-arm64
wheel-macos-monterey-cp39-cp39-amd64
wheel-macos-monterey-cp39-cp39-arm64

[kou]

+1

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 6c9e7e7.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.