Add a Python: New Project command

[karrtikr]

Creates and opens a new workspace folder set up for Python development. One way to do it could be:

• Prompts to enter path to project with prefilled input, similar to:
  
• Creates it and opens it as workspace
• Runs Create Environment and selects it for workspace
• (Optional) Creates a main.py entrypoint

We can use it in the first step of getting started to encourage users to start using projects and local environments, which right now isn't done if no project is already opened:

cc/ @cwebster-99

[karrtikr]

Based on discussion, "Project" can be interpreted to contain config files and more. As folder is meant to be empty, it's best if we use other terminology, "Workspace" instead could work better.

[luabud]

I really really like this idea and it's definitely something we hear as something folks missing when trying Python in VS Code for the first time.

[cwebster-99]

Aligning conversations for the most up to date direction for a Python: Create Project command. We currently have experimental support or new project creation when uv is installed. We want to build upon this API so any tool can provide a project creation flow, and we provide a default experience using pip if the user does not have a tool of choice installed.

We can follow the templates in vscode-python-templates for structure but our core default project templates should be:

• Package
• Script
• FastAPI
• Django
• Flask

I suggested we use the default Django project CLI commands to build the project but we may need to provide a default structure for FastAPI and Flask. We can reach out to FastAPI, Flask, and Django communities for feedback on our approach as well!

For each project, we should:

• Create and name a workspace folder
• Create a virtual environment
• Add a README.md
• Add tests subdirectory