feat(settings): add GitHub HTTP MCP server configuration

[katriendg]

Description

Added the GitHub HTTP MCP server to the VS Code workspace MCP configuration, enabling direct access to GitHub MCP tools via the GitHub Copilot API endpoint. This unlocks GitHub issue management and more, enabling the usage of the HVE-Core AI artifacts for enhanced issue tracking and management within the VS Code environment.

• feat(settings): added github MCP server entry in .vscode/mcp.json with HTTP transport type pointing to https://api.githubcopilot.com/mcp/

Related Issue

Closes #196

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Blueprint modification or addition
• Component modification or addition
• Documentation update
• CI/CD pipeline change
• Other (please describe):

Implementation Details

Added a new github server block to the existing MCP server definitions in .vscode/mcp.json. The server uses the http transport type with the GitHub Copilot MCP API URL (https://api.githubcopilot.com/mcp/). This complements the existing MCP server configurations (microsoft-docs, crisp, contex7, Azure DevOps) already defined in the workspace.

Testing Performed

• Terraform plan/apply
• Blueprint deployment test
• Unit tests
• Integration tests
• Bug fix includes regression test (see Test Policy)
• Manual validation
• Other: Manual verification of MCP server configuration in VS Code

Validation Steps

1. Open the workspace in VS Code
2. Verify the GitHub MCP server appears in the MCP server list
3. Confirm the server connects successfully via the HTTP transport

Checklist

• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have run terraform fmt on all Terraform code
• I have run terraform validate on all Terraform code
• I have run az bicep format on all Bicep code
• I have run az bicep build to validate all Bicep code
• I have checked for any sensitive data/tokens that should not be committed
• I have run MegaLinter on my code (mega-linter-runner)

🔧 - Generated by Copilot

[Copilot]

Pull request overview

Adds a workspace-level GitHub MCP server entry so VS Code/Copilot can access github/* MCP tools via the GitHub Copilot MCP HTTP endpoint.

Changes:

• Added a new github MCP server entry using http transport pointing to https://api.githubcopilot.com/mcp/.