GH-43845: [Docs] Update Python Development Build Instructions

[WillAyd]

Rationale for this change

Following along the documentation as is will yield the errors described in these issues:

#42006 (comment)
#41992 (comment)

What changes are included in this PR?

The documentation now uses the pip front end, rather than invoking setuptools directly

Are these changes tested?

Locally

Are there any user-facing changes?

Yes...unfortunately when following these instructions, users will now see:

DEPRECATION: --build-option and --global-option are deprecated. pip 24.2 will enforce this behaviour change. A possible replacement is to use --config-settings. Discussion can be found at https://github.com/pypa/pip/issues/11859
WARNING: Implying --no-binary=:all: due to the presence of --build-option / --global-option. 

The pyarrow setup script seems to need --build-type and --bundle-arrow-cpp as global options. Unfortunately, there is a disconnect between what pip offers and what setuptools can handle, so the only current way to pass these options to setuptools is through the front-end that pip has deprecated. A larger discussion and recap of the issue can be seen here:

pypa/pip#11859 (comment)

• GitHub Issue: [Python][Docs] Use editable pip install invocation in the development docs for PyArrow #43845

[WillAyd]

@jorisvandenbossche @assignUser if you have a chance to look - might be something easy I am missing

[jorisvandenbossche]

Thanks for looking into this. Updating those instructions was long overdue ..

[jorisvandenbossche]

Suggested change

	$ python -m pip install -e .
	$ python -m pip install -e . --no-build-isolation --no-deps -v

Those additional flags make it more similar to what we did before. It's probably debatable whether those should be added (disabling build isolation and installing deps), but since in this tutorial we have set up all build dependencies in advance, not doing that gives unnecessary pip overhead.
(this is also the command that I use locally, although for quick rebuilds I still use python setup.py build_ext --inplace)

[jorisvandenbossche]

Suggested change

	$ python -m pip wheel . \
	$ python -m build . \

Using https://build.pypa.io/en/stable/ might be the recommended way nowadays to build a wheel?

When using that, it might need --config-setting instead of --global-option (but haven't verified this works the same)

[WillAyd]

When using that, it might need --config-setting instead of --global-option (but haven't verified this works the same)

I believe the --global-option is a requirement as long as setuptools is the backend. It's extremely murky, but here's the best conversation I could find on that topic:

pypa/pip#11859 (comment)

[jorisvandenbossche]

Yes, we need some way to pass down the option, but what I meant is that when using python -m build instead of python -m pip wheel, the name of the keyword to pass options might be different.

Because in the docs of build, I only see --config-setting and not --global-option

[jorisvandenbossche]

Suggested change

	$ python pip install -e .
	$ python pip install -e . --no-build-isolation --no-deps -v

(depending on what is done above)

[github-actions]

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

[jorisvandenbossche]

(opened an issue for this, because it's not actually a minor change anymore)