[azsdk-cli] mcp tool `azsdk_verify_setup` does Not Reliably setup Python SDK Environments

`azsdk_verify_setup` does not reliably set up the Python SDK development environment. The issue is especially common on machines that already have Python installed and are not in a clean state.

During the setup process, the tool frequently encounters dependency conflicts, package resolution failures, or missing library issues. As a result, the Python SDK generation, build, and validation workflows often fail, preventing developers from successfully working with the generated SDK.

Expected Behavior

`azsdk_verify_setup` should be able to consistently create and configure a usable Python development environment. Preferably, it should create and use a clean, isolated .venv environment to avoid conflicts with existing Python installations and packages. After setup completes, developers should be able to successfully generate, build, and validate the Python SDK without additional manual environment fixes.

Start by running `azsdk_verify_setup` on a machine with an existing Python installation and observe dependency conflicts, resolution failures, or missing libraries. Trace the setup flow and its generated environment, then verify that a clean isolated `.venv` supports Python SDK generation, build, and validation without manual fixes.

Written by the indexing model from the issue text.