fix(scaffold): use cross-platform venv path in vscode settings

[qjrm1430]

Summary

• Drop the OS-specific bin/python suffix from python.defaultInterpreterPath in the scaffold's .vscode/settings.json
• Python extension now auto-resolves the interpreter for both Windows (Scripts/python.exe) and Linux/macOS (bin/python)

Test plan

• Generate a project via act new on Linux and confirm VS Code picks up .venv/bin/python
• Generate a project on Windows and confirm VS Code picks up .venv/Scripts/python.exe

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the VS Code settings template for scaffolded projects. It modifies the python.defaultInterpreterPath to point to the .venv directory instead of the Python executable. Feedback suggests removing this setting entirely, as pointing to a directory is invalid for the VS Code Python extension, and standard virtual environments like .venv are already auto-detected across platforms.

[gemini-code-assist]

Setting python.defaultInterpreterPath to a directory (${workspaceFolder}/.venv) is invalid because the VS Code Python extension expects a path to the Python executable (e.g., bin/python or Scripts/python.exe). Pointing it to a directory will cause VS Code to fail to resolve the interpreter, leading to errors when running Python tools, tests, or formatters.

Since the VS Code Python extension automatically detects standard virtual environments like .venv in the workspace root on all platforms (Windows, macOS, and Linux), the best cross-platform solution is to omit this setting entirely.

Suggested change

	"python.defaultInterpreterPath": "${workspaceFolder}/.venv",
	"python.testing.pytestEnabled": true,
	"python.testing.pytestEnabled": true,