feat: comfyui create venv as needed

[Interpause]

Fixes #263, #272.

As comfy-cli might be installed globally via pipx or uv, as per linked issue, it ends up installing the comfyui dependencies into the managed environment. Especially since comfy-cli can manage several comfyui installs, it should install into environments per each install. Hence the below logic:

1. If .venv/venv is present in comfyui folder, use that.
2. If a Conda environment is currently active, use that.
3. Create .venv using the currently active Python in --copies mode to prevent broken symlinks if user were to later delete that Python version.

I have thus far tested only on Linux, but I assume it should work for MacOS and Windows too. That said, I only tested if comfy install and comfy launch work as expected.

I tried to selectively change sys.executable to use the venv where appropriate. However, as I am new to this codebase, I might have missed out some places or changed some places I should not, so I need help to check that. The riskiest part, comfy standalone seems to be broken for me before I made my changes, so I can't tell if I may have broke that.

Also, while this approach works perfectly fine for venvs, it is limited for Conda environments. Since it doesn't properly activate Conda, tools installed in the Conda environment like nvcc aren't available as expected. I think this can be solved as a separate issue.

[Interpause]

Fixed the merge conflicts; Haven't tested if the PR still works on any of Linux, Mac or Windows though cause its been a while since I last used comfyui. Change from draft to open to hopefully increase visibility. Am open to fixing any new bugs since June.

[geroldmeisinger]

bump

[bigcat88]

1. venv creation is too eager

find_or_create_python_env() is called in setup_workspace_manager(), which runs on every command via the main callback. This means:

• Running comfy env or even comfy --help could trigger venv creation
• Running comfy install for a fresh install would fail because the workspace directory doesn't exist yet

My suggestion: Make venv creation lazy - only create when actually needed (e.g., during install, launch, update), or/and add a guard:

if self.workspace_path and os.path.isdir(self.workspace_path):
    self.python_exe = self.find_or_create_python_env()
else:
    self.python_exe = sys.executable  # fallback

2. No workspace existence check

The function doesn't verify self.workspace_path exists before trying to create a venv in it:
os.path.join(self.workspace_path, default_name) # Could fail if workspace_path is None or doesn't exist

3. --upgrade-deps requires network

This downloads the latest pip/setuptools during venv creation. It will:

• Fail in offline environments
• Slow down venv creation