docs: Remove 'pip install' options in recipes

[matthewfeickert]

• Remove --no-deps, --no-build-isolation, and --ignore-installed pip install options in recipes as conda-build will enforce all required pip install options itself at build time.

c.f.

conda-build/conda_build/build.py

Lines 3020 to 3024 in 0ad4bb6

	env["PIP_NO_BUILD_ISOLATION"] = "False"
	# some other env vars to have pip ignore dependencies.
	# we supply them ourselves instead.
	env["PIP_NO_DEPENDENCIES"] = True
	env["PIP_IGNORE_INSTALLED"] = True

• c.f. Question: why is --no-deps --no-build-isolation set? grayskull#582 for motivation and discussion.

• Reverts Conform to recipe standards #4960

Description

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[conda-bot]

We require contributors to sign our Contributor License Agreement and we don't have one on file for @matthewfeickert.

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#1062), and ping the bot to refresh the PR.

[matthewfeickert]

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#1062), and ping the bot to refresh the PR.

I've signed the CLA. Please merge conda/infrastructure#1062.

[jezdez]

@conda-bot check

[codspeed-hq]

CodSpeed Performance Report

Merging #5541 will not alter performance

_{Comparing matthewfeickert:docs/remove-pip-install-options (9be669d) with main (0ad4bb6)}

Summary

✅ 5 untouched benchmarks

[matthewfeickert]

Thanks for taking care of my CLA, @jezdez. This is ready for review now.

cc @beckermr @kenodegard also given their recent PR review/merge activity.

[jezdez]

@matthewfeickert Could you please open a ticket that describes the overarching reason we're doing this, basically what is being discussed in conda/grayskull#582? This would be for record-keeping that this is an ecosystem-wide alignment to remove the explicit pip arguments.

[jezdez]

Thanks for taking care of my CLA, @jezdez. This is ready for review now.

cc @beckermr @kenodegard also given their recent PR review/merge activity.

No need to cc anyone, the @conda/builds-tools is automatically assigned and informed.

[matthewfeickert]

Could you please open a ticket that describes the overarching reason we're doing this

Sure. Done in Issue #5543.

No need to cc anyone, the @conda/builds-tools is automatically assigned and informed.

Ah cool. I didn't realize that conda had a similar teams system to conda-forge. 👍

[beckermr]

LGTM from me, but we should wait for others.