GH-48419: [Python] Fix test_parquet_file_too_small to catch only ArrowInvalid

[HyukjinKwon]

Rationale for this change

The test does not throw OSError anymore.

What changes are included in this PR?

This PR changes test_parquet_file_too_small test to only catch ArrowInvalid.

Are these changes tested?

Yes, manually tested via

pytest pyarrow/tests/parquet/test_basic.py::test_parquet_file_too_small

Are there any user-facing changes?

No, test-only.

• GitHub Issue: [Python] Fix test_parquet_file_too_small to catch only ArrowInvalid #48419

[github-actions]

⚠️ GitHub issue #48419 has been automatically assigned in GitHub to PR creator.

[raulcd]

@github-actions crossbow submit -g python

[raulcd]

LGTM, I am just running extended tests for CI coverage just in case. Will merge once CI is successful

[github-actions]

Revision: 9950dc5

Submitted crossbow builds: ursacomputing/crossbow @ actions-ebe47310ef

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-1.3.4-numpy-1.21.2
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-latest
test-conda-python-3.11-spark-master
test-conda-python-3.12
test-conda-python-3.12-cpython-debug
test-conda-python-3.12-pandas-latest-numpy-1.26
test-conda-python-3.12-pandas-latest-numpy-latest
test-conda-python-3.13
test-conda-python-3.13-pandas-nightly-numpy-nightly
test-conda-python-3.13-pandas-upstream_devel-numpy-nightly
test-conda-python-3.14
test-conda-python-emscripten
test-cuda-python-ubuntu-22.04-cuda-11.7.1
test-cuda-python-ubuntu-24.04-cuda-13.0.2
test-debian-12-python-3-amd64
test-debian-12-python-3-i386
test-fedora-42-python-3
test-ubuntu-22.04-python-3
test-ubuntu-22.04-python-313-freethreading
test-ubuntu-24.04-python-3

[raulcd]

CI failures are unrelated.

[HyukjinKwon]

Thank you @raulcd !!!

[conbench-apache-arrow]

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

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.