NumPy 2.0 is coming soon, and we should ensure pyarrow is fully compatible to ensure a smooth transition of our users. Overview issue on numpy's side: numpy/numpy#24300

We already test with nightly numpy (eg https://github.com/ursacomputing/crossbow/actions/runs/7454906275/job/20283098411), and currently this build is working fine.
There is one warning about the usage of numpy.core.numerictypes that we should still solve.

Further, we need to check if we are all OK on the packaging side: do we need to pin numpy<2 for now in our upcoming release? What do we need to update in our wheel building? (stop using oldest-supported-numpy?)

• [Python] NumPy 2.0 compat: remove usage of np.core #39533
• [Packaging][Python] Add a numpy<2 pin to the install requirements in the release branch #39537
• [Packaging][Python] Enable building pyarrow against numpy 2.0 #39555
  • Ensure we can build pyarrow against numpy 2.0 nightly (update pyproject.toml to allow this), and test this by building our nightly wheels with numpy nightly
  • [CI][Python] The pandas upstream_devel nightly build is skipping all pandas tests #39536
  • [Python][Packaging] Remove nightly numpy wheels from the wheel build requirements #39848
• [Python] Adapt to changes in the copy keyword for numpy 2.0+ compatibility #41098
• [Python] NumPy 2 ABI changes (elsize) #40376

cc @raulcd