GH-46349: [Python] Move parquet definitions to pyarrow/includes/libparquet.pxd

[raulcd]

Rationale for this change

Follow the convention we have for Arrow C++ API declarations which are are stored in pyarrow/includes/libxxx.pxd, with the specific name depending on the C++ component (for example pyarrow/includes/libarrow_dataset.pxd).
This follows the architecture defined:
https://arrow.apache.org/docs/python/getting_involved.html#pyarrow-architecture

What changes are included in this PR?

Move the Parquet C++ API declarations to pyarrow/includes/libparquet.pxd.

Are these changes tested?

Yes via CI and archery extended Python jobs.

Are there any user-facing changes?

No

• GitHub Issue: [Python] pyarrow/_parquet.pxd should go into pyarrow/includes #46349

[raulcd]

@github-actions crossbow submit -g python

[raulcd]

@github-actions crossbow submit wheelcp311

[raulcd]

@github-actions crossbow submit -g python

[raulcd]

@github-actions crossbow submit wheelcp310

[github-actions]

Revision: 83dbbab

Submitted crossbow builds: ursacomputing/crossbow @ actions-1299dc12ed

Task	Status
wheel-macos-monterey-cp310-cp310-amd64
wheel-macos-monterey-cp310-cp310-arm64
wheel-manylinux-2-28-cp310-cp310-amd64
wheel-manylinux-2-28-cp310-cp310-arm64
wheel-manylinux-2014-cp310-cp310-amd64
wheel-manylinux-2014-cp310-cp310-arm64
wheel-musllinux-1-2-cp310-cp310-amd64
wheel-musllinux-1-2-cp310-cp310-arm64
wheel-windows-cp310-cp310-amd64

[github-actions]

Revision: 83dbbab

Submitted crossbow builds: ursacomputing/crossbow @ actions-84c0dabebe

Task	Status
example-python-minimal-build-fedora-conda
example-python-minimal-build-ubuntu-venv
test-conda-python-3.10
test-conda-python-3.10-hdfs-2.9.2
test-conda-python-3.10-hdfs-3.2.1
test-conda-python-3.10-pandas-latest-numpy-latest
test-conda-python-3.11
test-conda-python-3.11-dask-latest
test-conda-python-3.11-dask-upstream_devel
test-conda-python-3.11-hypothesis
test-conda-python-3.11-pandas-latest-numpy-1.26
test-conda-python-3.11-pandas-latest-numpy-latest
test-conda-python-3.11-pandas-nightly-numpy-nightly
test-conda-python-3.11-pandas-upstream_devel-numpy-nightly
test-conda-python-3.11-spark-master
test-conda-python-3.12
test-conda-python-3.12-cpython-debug
test-conda-python-3.13
test-conda-python-3.9
test-conda-python-3.9-pandas-1.1.3-numpy-1.19.5
test-conda-python-emscripten
test-cuda-python-ubuntu-22.04-cuda-11.7.1
test-debian-12-python-3-amd64
test-debian-12-python-3-i386
test-fedora-39-python-3
test-ubuntu-22.04-python-3
test-ubuntu-22.04-python-313-freethreading
test-ubuntu-24.04-python-3

[pitrou]

+1, thank you @raulcd

[conbench-apache-arrow]

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

There were no benchmark performance regressions. 🎉

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