Remove python mcp and associated copilot instructions (moving to azsdkcli) (#43121)

* remove python mcp files

* copilot instr remove

Author: l0lawrence

.github/copilot-instructions.md

@@ -16,180 +16,6 @@
 **REQUIRED CONDITIONS:**
 - To use Azure MCP tool calls, users must have PowerShell installed. Provide [PowerShell installation instructions](https://learn.microsoft.com/powershell/scripting/install/installing-powershell) if not installed, and recommend restarting the IDE to start the MCP server.
 
-**BEFORE any commands:**
-1. Get path to azure-sdk-for-python repo root, and path to tox.ini file
-2. Use `verify_setup` tool from azure-sdk-python-mcp server
-3. Ensure Python virtual environment is active
-
-**Virtual Environment Setup:**
-```bash
-# Create new environment
-python -m venv <env_name>
-
-# Activate environment
-# Linux/macOS:
-source <env_name>/bin/activate
-# Windows:
-<env_name>\Scripts\activate
-```
-
----
-
-## TYPESPEC SDK GENERATION - COMPLETE WORKFLOW
-
-### PHASE 1: CONTEXT ASSESSMENT
-
-**ACTION:** Determine TypeSpec project location
-```
-IF TypeSpec project paths exist in context:
-    USE local paths to generate SDK from tspconfig.yaml
-ELSE:
-    ASK user for tspconfig.yaml file path
-```
-
-### PHASE 2: PREREQUISITES CHECK
-
-**REQUIRED CONDITIONS:**
-1. GitHub CLI authenticated: `gh auth login`
-2. User on feature branch (NOT main)
-   ```bash
-   git checkout -b <branch_name>
-   ```
-
-### PHASE 3: TSP-CLIENT RULES
-
-**CRITICAL RULES:**
-- **LOCAL REPO:** Do NOT grab commit hash
-- **DIRECTORIES:** Let commands auto-create directories
-- **PACKAGE GENERATION:** Find tsp-location.yaml in azure-sdk-for-python repo
-- **URL REFERENCES:** Use commit hash (NOT branch name) for tspconfig.yaml URLs
-
-**Get latest commit hash:**
-```bash
-curl -s "https://api.github.com/repos/Azure/azure-rest-api-specs/commits?path=<path_to_tspconfig.yaml>&per_page=1"
-```
-
-**DEPENDENCIES:** Verify installation of: node, python, tox
-
----
-
-## EXECUTION SEQUENCE - 7 MANDATORY STEPS
-
-**ESTIMATED TOTAL TIME: 10-15 minutes**
-- SDK Generation: ~2 minutes
-- Static Validation: ~3-5 minutes
-- Documentation & Commit: ~2-4 minutes
-
-**ALWAYS inform users of time expectations before starting any long-running operations.**
-
-### STEP 1: ENVIRONMENT VERIFICATION
-```
-ACTION: Run verify_setup mcp tool
-IF missing dependencies:
-    STOP and install missing dependencies
-    THEN proceed to Step 2
-```
-
-### STEP 2: SDK GENERATION
-```
-ACTION: Use azure-sdk-python-mcp sdk generation server tools (init for new packages, update for existing packages)
-IF commands fail:
-    ANALYZE error messages
-    DIRECT user to fix TypeSpec errors in source repo
-```
-
-### STEP 3: STATIC VALIDATION (SEQUENTIAL)
-```
-FOR EACH validation step:
-    RUN validation (tox mcp tool)
-    IF errors/warnings found:
-        FIX issues
-        RERUN same step
-    ONLY proceed to next step when current step passes
-```
-
-**Validation Commands:**
-```bash
-# Step 3a: Pylint
-tox -e pylint -c [path to tox.ini] --root .
-
-# Step 3b: MyPy  
-tox -e mypy -c [path to tox.ini] --root .
-
-# Step 3c: Pyright
-tox -e pyright -c [path to tox.ini] --root .
-
-# Step 3d: Verifytypes
-tox -e verifytypes -c [path to tox.ini] --root .
-
-# Step 3e: Sphinx
-tox -e sphinx -c [path to tox.ini] --root .
-
-# Step 3f: Mindependency
-tox -e mindependency -c [path to tox.ini] --root .
-
-# Step 3g: Bandit
-tox -e bandit -c [path to tox.ini] --root .
-
-# Step 3h: Black
-tox -e black -c [path to tox.ini] --root .
-
-# Step 3i: Samples
-tox -e samples -c [path to tox.ini] --root .
-
-# Step 3j: Breaking
-tox -e breaking -c [path to tox.ini] --root .
-```
-
-**REQUIREMENTS:**
-- Provide summary after each validation step
-- Edit ONLY files with validation errors/warnings
-- Fix each issue before proceeding
-
-### STEP 4: DOCUMENTATION UPDATE
-```
-REQUIRED ACTIONS:
-1. CREATE/UPDATE CHANGELOG.md with changes
-2. VERIFY package version matches API spec version
-3. IF version incorrect: UPDATE _version.py AND CHANGELOG
-4. SET CHANGELOG entry date to TODAY
-```
-
-### STEP 5: COMMIT AND PUSH
-```
-ACTION: Show changed files (ignore .github, .vscode)
-IF user confirms:
-    git add <changed_files>
-    git commit -m "<commit_message>"
-    git push -u origin <branch_name>
-IF authentication fails:
-    PROMPT: gh auth login
-IF user rejects:
-    GUIDE to fix issues and revalidate
-```
-
-### STEP 6: PULL REQUEST MANAGEMENT
-```
-CHECK: Does PR exist for current branch?
-IF PR exists:
-    SHOW PR details
-IF NO PR exists:
-    VERIFY branch != "main"
-    PUSH changes to remote
-    GENERATE PR title and description
-    CREATE PR in DRAFT mode
-    RETURN PR link
-ALWAYS: Display PR summary with status, checks, action items
-```
-
-### STEP 7: HANDOFF
-```
-FINAL ACTIONS:
-1. RETURN PR URL for review
-2. PROMPT user with exact text:
-   "Use the azure-rest-api-specs agent to handle the rest of the process and provide it the pull request."
-```
-
 ---
 
 ## PYLINT OPERATIONS

.vscode/mcp.json

@@ -1,16 +1,5 @@
 {
     "servers": {
-        "azure-sdk-python-mcp": {
-            "command": "uv",
-            "args": [
-                "run",
-                "--index-url",
-                "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-python/pypi/simple/",
-                "--with",
-                "azure-sdk-python-mcp",
-                "azure-sdk-python-mcp"
-            ],
-        },
         "azure-sdk-mcp": {
             "type": "stdio",
             "command": "pwsh",