[Python] Jobs fail if Pyarrow version is not correctly generated due to missing remote dev tags

[raulcd]

Describe the bug, including details regarding any error messages, version, and platform.

Sometimes we get some job failures when a contributor makes a PR and their remote git repository does not contain development tags.
The pyarrow generated version on those cases looks like pyarrow-0.1.dev16896+ge3b9892.
An example of this issue can be seen on this comment: #44720 (comment)
and the build fails with:

self = <[AttributeError("'ArrowDtype' object has no attribute 'pyarrow_dtype'") raised in repr()] ArrowDtype object at 0x7f5b9b45f610>
pyarrow_dtype = DataType(int64)

 def __init__(self, pyarrow_dtype: pa.DataType) -> None:
 super().__init__("pyarrow")
 if pa_version_under10p1:
> raise ImportError("pyarrow>=10.0.1 is required for ArrowDtype")
E ImportError: pyarrow>=10.0.1 is required for ArrowDtype

on the:

• example-python-minimal-build-fedora-conda
• example-python-minimal-build-ubuntu-venv

We should find a workaround for those cases instead of having to tell users to push tags to their remote.

Component(s)

Python

[dinse]

Hello, I ran into this problem while running pytests for a first issue.

Before finding the instructions to fetch tags from upstream, I also got the tests to pass via

SETUPTOOLS_SCM_PRETEND_VERSION='21.0.0' python setup.py build_ext --inplace
SETUPTOOLS_SCM_PRETEND_VERSION='21.0.0' python -m pytest pyarrow

Since this appears to be a recurring issue, would it be appropriate for the time being to update the documentation to mention dev tags in either "Steps in making your first PR/Set Up", or "Python Development/Unit Testing"?