docs: Upgrading Core links to Express links isn't always wanted

[gadenbuie]

The quartodocs rendering process finds shiny.ui.___ links and upgrades them to shiny.express.ui.____ links

py-shiny/docs/_renderer.py

Lines 61 to 72 in ea5db0e

	converted = converted.replace("shiny.ui.", "shiny.express.ui.")
	# If this el happens to point to itself, it's probably intentionally
	# pointing to Core (i.e., express context managers mention that they
	# wrap Core functions), so don't change that.
	# TODO: we want to be more aggressive about context managers always
	# pointing to the Core docs?
	if f"shiny.express.ui.{el.name}" in converted:
	print(f"Changing Express link to Core for: {el.name}")
	converted = converted.replace(
	f"shiny.express.ui.{el.name}", f"shiny.ui.{el.name}"
	)
	converted = converted.replace("shiny.render.", "shiny.express.render.")

but this isn't always desirable, as in the case of :func:`~shiny.ui.page_auto` which only exists in shiny.ui. When the Express counterpart doesn't exist, the function is rendered as code without a link. See https://shiny.posit.co/py/api/express/express.ui.page_opts.html

[schloerke]

I'm ok if we white list exceptions until a bigger pattern emerges. The docs handling code doesn't need to be pretty

[cpsievert]

Maybe we could try importing converted using something like this, then informatively warn/error if it doesn't exist?

[gadenbuie]

...or just use the original link if the converted link doesn't exist.