Add Env Setup to Copilot Instructions

[JennyPng]

Azure/azure-sdk-tools#12592

explicit:

before running another tool:

non-mcp related queries (it doesn't try to run the tool)

ack:

• We want this check to be proactive and happen without explicit invokation. However, currently, Copilot would only remember if the tool is run in the current session, not in newer sessions, so it could be annoying for the user to constantly have to verify setup in new sessions due to a lack of a caching. This will be accepted for Scenario 1 and improved in future iterations
• LLM performs better with the relative link to instructions

[Copilot]

Pull Request Overview

This PR updates the Copilot instructions to enforce environment verification before proceeding with development operations. The change adds a mandatory step to run the azsdk_verify_setup tool to validate the user's development environment.

Key Changes

• Adds a requirement to run azsdk_verify_setup tool before any other operations in Rule 3

[maririos]

• In the context of a repo, is the language passed to the request, so the tool doesn't verify environment conditions that don't apply? like .NET tooling for Python work.
• Curious, what does classify as an operation?
• How much time is added to the process if this is going to run in every operation?

[JennyPng]

• In the context of a repo, is the language passed to the request, so the tool doesn't verify environment conditions that don't apply? like .NET tooling for Python work.
• Curious, what does classify as an operation?
• How much time is added to the process if this is going to run in every operation?

@maririos

• Yes, the tool should only check Python (and core) requirements in the Python repo, unless the user explicitly specifies other languages
• My intention is for Copilot to suggest this tool before running other MCP tools in the current session - operation isn't really an official term, I'll reword this part actually; in general I just struggled to find terms that would make Copilot actually do what I wanted it to do
• From my testing so far, it suggests to verify setup at the start of the session - but if the user stays in the session and continues requesting other MCP tools, it doesn't try to run it again. Depending on the language, the tool around 3-15 seconds?

[JennyPng]

/check-enforcer override