feat: generate AI coding agent artifacts for prometheus-collector

[ganga1980]

Auto-generated agent artifacts for AI coding assistants (GitHub Copilot, Jules, Gemini CLI, etc.).

Includes:

• .github/copilot-instructions.md — root router with build instructions and guidelines
• AGENTS.md — setup commands, code style, testing, PR instructions
• Prompt.md — reusable task-spec template
• .github/instructions/ — auto-activating rules for Go, TypeScript, Dockerfile, Kubernetes
• .github/skills/ — 9 skills (dependency-update, test-authoring, bug-fix, feature-development, ci-cd-pipeline, infrastructure, security-review, telemetry-authoring, fix-critical-vulnerabilities)
• .github/agents/ — CodeReviewer, SecurityReviewer, ThreatModelAnalyst, DocumentWriter, prd agents
• .vscode/mcp.json — GitHub and Microsoft Docs MCP server config
• otelcollector/test/AGENTS.md — test framework guide
• coding-agent-instructions.md — comprehensive usage guide

PR Description

New Feature Checklist

• List telemetry added about the feature.
• Link to the one-pager about the feature.
• List any tasks necessary for release (3P docs, AKS RP chart changes, etc.) after merging the PR.
• Attach results of scale and perf testing.

Tests Checklist

• Have end-to-end Ginkgo tests been run on your cluster and passed? To bootstrap your cluster to run the tests, follow these instructions.
  • Labels used when running the tests on your cluster:
    • operator
    • windows
    • arm64
    • arc-extension
    • fips
• Have new tests been added? For features, have tests been added for this feature? For fixes, is there a test that could have caught this issue and could validate that the fix works?
  • Is a new scrape job needed?
    • The scrape job was added to the folder test-cluster-yamls in the correct configmap or as a CR.
  • Was a new test label added?
    • A string constant for the label was added to constants.go.
    • The label and description was added to the test README.
    • The label was added to this PR checklist.
    • The label was added as needed to testkube-test-crs.yaml.
  • Are additional API server permissions needed for the new tests?
    • These permissions have been added to api-server-permissions.yaml.
  • Was a new test suite (a new folder under /tests) added?
    • The new test suite is included in testkube-test-crs.yaml.

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This PR was closed because it has been stalled for 12 days with no activity.