docs: explain Jupyter blank-render workaround

[tomatotomata]

What changed

I added a short Jupyter and JupyterLab troubleshooting section to the existing troubleshooting page. It calls out the separate-server and kernel environment setup, then documents the fig.show(renderer=notebook) workaround from #5664.

This is intentionally documentation only. It does not claim to fix the underlying blank-render bug.

Validation

• git diff --check passed
• The repository's docs conversion tool was not available locally, so the full notebook build was not run

This follows the scope suggested in #5664. Let me know what you think.

Closes #5664

[camdecoster]

Thanks for the update! This will be a helpful addition. Could you please move this section to the end of the document?

[camdecoster]

Suggested change

	If a figure appears blank in JupyterLab, first check that the Jupyter server
	environment and the environment used by the notebook kernel can both access the
	Plotly packages they need. This is especially important when JupyterLab and
	`plotly` are installed in separate virtual environments.
	If a figure appears blank in JupyterLab, first check that the Jupyter server environment and the environment used by the notebook kernel can both access the Plotly packages they need. This is especially important when JupyterLab and `plotly` are installed in separate virtual environments.

[tomatotomata]

I moved the Jupyter and JupyterLab section to the end of doc/python/troubleshooting.md in 846b3674c. The content is unchanged, so the page now follows the ordering you requested without widening the scope. git diff --check is clean. Let me know what you think.

[camdecoster]

Could you please update this to all be on one line? That matches the style of the document.

[tomatotomata]

I updated the troubleshooting paragraph in bb4dd0b24 so the sentence stays on one line, matching the document style. git diff --check passes. Let me know what you think.

[tomatotomata]

I also rebased the PR onto current main at 304fb763e, keeping its current Orca wording and the requested one-line Jupyter troubleshooting paragraph. The refreshed head is 10961d98e; git diff --check passes, and GitHub now reports the PR as mergeable again. The Orca security check is queued on this head. Let me know what you think.