feat: add GitHub HTTP MCP server to unlock HVE-Core OSS tooling

[katriendg]

Problem Statement

The repository already leverages several MCP servers (Terraform, Context7, Microsoft Docs, Azure DevOps, CRISP) for developer productivity, but lacks a GitHub MCP server. The HVE-Core extension (ise-hve-essentials.hve-core) is already installed in this devcontainer and ships AI artifacts that depend on a github MCP server being available:

• github-issue-manager agent declares 'github/*' in its tools list for conversational issue filing, navigation, and search
• github-add-issue prompt provides guided issue creation via discovered templates
• pr-review agent supports PR review workflows

Without the GitHub MCP server registered in .vscode/mcp.json, these HVE-Core artifacts cannot access the github/* tools they require, leaving GitHub-native operations (issue triage, PR management, code search) inaccessible from the AI-assisted workflow.

Proposed Solution

Add the GitHub MCP Server as an HTTP-based MCP server entry in .vscode/mcp.json to unlock the existing HVE-Core AI artifacts.

Configuration addition to .vscode/mcp.json:

"github": {
  "type": "http",
  "url": "https://api.githubcopilot.com/mcp/"
}

This single configuration change enables the full suite of HVE-Core GitHub tooling already bundled with the devcontainer — no new prompts, agents, or instructions need to be created or modified.

Target Components

• Terraform modules
• Bicep modules
• Blueprints
• GitHub Actions
• Documentation
• Other: .vscode/mcp.json

Implementation Ideas

• Add the github server entry to .vscode/mcp.json alongside the existing MCP servers