Add SDK Workflow section to copilot-instructions.md linking to azsdk-tools

[Copilot]

Added a new SDK Workflow section to .github/copilot-instructions.md that links to the eng/common/instructions/azsdk-tools folder for SDK generation, development, verification, and release workflows.

Changes

• Added ## SDK Workflow section with relative path link to ../eng/common/instructions/azsdk-tools
• Positioned before the existing SDK release section for logical flow
• All existing content preserved

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• scanning-api.github.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

I want to update the copilot-instruction files for azure-sdk-for-python, azure-sdk-for-go, azure-sdk-for-java, azure-sdk-for-js, azure-sdk-for-net, and azure-rest-api-specs so that they link to eng/common/instructions/azsdk-tools instruction files regarding the azsdk mcp server tooling. do not replace the exisiting content of these files, we can use the relative path to the folder, and we should accompany the link with something along the lines of " # SDK Workflow \n For anything related to sdk generation/development/verification/release see here (link to folder)"

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.