Improve algokit bootstrap compatibility with conda based python virtual environments

[aorumbayev]

Problem

Certain scenarios when user creates an algokit project from a template may yield inconsistent behaviour when a user runs bootstrap within already active virtual environment. Certain templates and repos in algokit ecosystem rely on existence of .venv defined at the root of the project.

Solution

Spike optimal ways to solve the compatibility issues with conda:

1. CLI changes to account for conda scenarios during boostrap
2. Per repo based python scripts that are references in vscode tasks to be used instead of direct invocation of python from expected .venv folders from the workspace root
3. Interactively prompt the user whether they want explicit .venv at the root during bootstrap if bootstrap detects that it was run within an active conda venv
4. Expand documentation to cover separate setup scenario when dealing with conda

Dependencies