GH-32609: [Python] Incorporate zen-xu/pyarrow-stubs for typing

[paddyroddy]

Rationale for this change

Currently, PyArrow is not typed and users have to use the stubs provided by https://github.com/zen-xu/pyarrow-stubs. This is not ideal and requires extra effort by zen-xu who has already expressed desire in donating his library (see zen-xu/pyarrow-stubs#186). Will fix apache#32609.

What changes are included in this PR?

This PR includes:

• A py.typed file to signify that the library is typed (fixes [Python] pyarrow missing py.typed marker file apache/arrow#33113)
• Incorporate the stub files from https://github.com/zen-xu/pyarrow-stubs
• CI following the NumPy mechanisms ENH: add type stubs from numpy-stubs numpy/numpy#16515
• A type checker (one of https://github.com/python/mypy, https://github.com/microsoft/pyright, https://github.com/facebook/pyrefly, https://github.com/astral-sh/ty). Currently favouring https://github.com/astral-sh/ty.

Are these changes tested?

They will be in a similar mechanism to the workflows NumPy has (.github/workflows/mypy.yml, .github/workflows/mypy_primer.yml, .github/workflows/mypy_primer_comment.yml).

Are there any user-facing changes?

The users will now have types!

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

[github-actions]

❌ GitHub issue apache#32609 could not be retrieved.

[paddyroddy]

Closing in favour of #3 as history is polluted