Python command not available in Workbench sessions without explicit launcherEnvPath configuration

Problem

There is a bug in the team-operator implementation where the python command is not directly available in Workbench sessions (RStudio or Positron) unless we explicitly specify the PATH of a Python version in the Site Spec as launcherEnvPath.

Python is properly installed on the system - the Python versions are visible and selectable when launching Jupyter sessions. However, there is no default Python configuration in either RStudio or Positron, making the python command unavailable in terminal sessions or when running Python scripts.

Expected Behavior

The python command should be available by default in Workbench sessions without requiring manual PATH configuration in the Site Spec.

Current Workaround

Manually specify the Python PATH in the Site Spec using the launcherEnvPath configuration.

Proposed Solution

The team-operator should automatically configure a default Python PATH for Workbench sessions, similar to how it's handled for Jupyter sessions.

Migrated from rstudio/ptd#2380

Start by tracing how the team-operator configures environment paths for Jupyter sessions and compare that with Workbench session setup for RStudio and Positron. Verify the behavior with and without launcherEnvPath; done means the python command is available in Workbench terminals and when running Python scripts without manual PATH configuration.