Deprecate conda.core.initalize.run_plan_elevated

[travishathaway]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

See this issue for some more context:

• Fresh install of conda on ubuntu 22.04 fails to init #13423

When conda encounters a problem with modifying a file during initialization, it will mark it as NEEDS_SUDO:

conda/conda/core/initialize.py

Lines 791 to 803 in 4963cf9

	def run_plan(plan):
	for step in plan:
	previous_result = step.get("result", None)
	if previous_result in (Result.MODIFIED, Result.NO_CHANGE):
	continue
	try:
	result = globals()[step["function"]](
	*step.get("args", ()), **step.get("kwargs", {})
	)
	except OSError as e:
	log.info("%s: %r", step["function"], e, exc_info=True)
	result = Result.NEEDS_SUDO
	step["result"] = result

The problem occurs later when we make the sudo call:

conda/conda/core/initialize.py

Lines 855 to 860 in 4963cf9

	result = subprocess_call(
	"sudo %s -m conda.core.initialize" % sys.executable,
	env={},
	path=os.getcwd(),
	stdin=stdin,
	)

We believe this behavior is problematic (currently does not work on unix-like systems) and would like to deprecate this functionality.

[jaimergp]

See also #12087, conda/menuinst#143. I think there are reasons to auto-elevate, but it might require a more robust workflow.

[travishathaway]

xref: #13472