[Doc] Remove dependency on PyArrow from rst build process

[asfimport]

The process for building the tutorial documentation (see: apache/arrow/docs/source/developers/documentation.rst) identifies PyArrow as a requirement

Ideally, it would not be necessary to install PyArrow to modify text documentation for Java or any other language. 

FWIW, On my machine, the PyArrow install has been running for over 20 minutes with repeated failure messages:

conda install -c conda-forge pyarrow

Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |

At this point I cancelled this and used pip to install, which finished successfully almost immediately. However, the next step (run {}python setup.py install{}) also failed. And failed again when I tried to run it in a dedicated Conda environment.  

Rather than continue with that, I tried to run the java documentation script: (run make java_tutorial in the arrow docs folder) and it was able to execute without issue, so I could see my changes as HTML.  

Reporter: Larry White / @lwhite1

Related issues:

• [Python][Docs] Enable building documentation with pyarrow nightly builds (relates to)

_{Note: This issue was originally created as ARROW-17819. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
cc @jorisvandenbossche

[asfimport]

Joris Van den Bossche / @jorisvandenbossche:
This is currently indeed an issue with our documentation. High-level, we have two related issues that can help with this:

• ARROW-13159: removing the use of the IPython directive (and thus from running code examples while building he docs) should help allowing building the python docs without an actual pyarrow installation (in addition, we would need to allow to skip the reference docs)

• ARROW-15117: splitting our docs in multiple sphinx projects, so that the python docs is a separate doc build, and thus you can build for example the developer docs without having to also build the python docs

  Short term, there are actually some workarounds to build a part of the docs, which is documented here: https://arrow.apache.org/docs/dev/developers/documentation.html#building-a-single-directory-for-dev-purposes-without-all-the-pre-requisites

[asfimport]

Joris Van den Bossche / @jorisvandenbossche:
BTW, for the conda install taking a long time: that's a common issue if you already have a complex environment. In general I would recommend to use mamba instead (but let's move this conversation elsewhere)

[AlenkaF]

Duplicate of #35906

[AlenkaF]

This issue was fixed with #35907