Copilot: Add pre-commit telemetry warnings for environment-specific failures

## Feature Request: Copilot Pre-Commit Telemetry for Environment Failures

### Background
I'm 52 years old and code 16 hours/day on Android/Termux as I transition into tech.

I'm the author of "Implementation of a Direct Telemetry Channel from the AI", a proposal I submitted directly to Google addressing the lack of real-time feedback from AI systems. The same proposal is now being refined by Hugging Face Regulars, confirming this is an industry-wide gap.

This gap exists in GitHub Copilot today. Last week I lost 400 CI runs + 2 days because I pushed a `kivy.core.window` import that works locally but breaks on Termux ARM64. My team at Meta spent hours debugging.

I had no way to know it would fail. But Copilot was reading my code the whole time.

### The Problem
Copilot already parses my repo and knows my environment. Yet it stays silent while I commit code that will 100% fail in CI. There's zero pre-commit telemetry.

### Proposed Solution
Before `git commit`, Copilot should surface warnings it can already detect:
`⚠️ Telemetry Alert: kivy.core.window will fail on ARM64/Termux - use Window instead`

### Why This Matters
1. **Saves compute**: Prevents thousands of wasted CI runs across the industry
2. **Industry standard**: I proposed this telemetry concept to Google. Microsoft can lead by shipping it first in Copilot.
3. **Dev experience**: Turns Copilot from autocomplete into a real pair programmer

If Google implements telemetry for their AI filters and Microsoft implements it for Copilot, we eliminate an entire class of wasted developer time.