Add Bernstein to Development MCPs

[chernistry]

Adds Bernstein to MCPs → Development MCPs as a multi-agent orchestrator MCP server.

Context

Re-submission after #48 (which itself reopened #42). @colbytimm closed those because GitHub Copilot wasn't visible in Bernstein's README. That has since been fixed:

• Bernstein has shipped a Copilot CLI adapter (src/bernstein/adapters/copilot.py, registered in src/bernstein/adapters/registry.py) — it was just missing from the README.
• README adapter table now lists GitHub Copilot CLI explicitly (commit 17c00428).
• Discussion: #48 closing reply showing the registry entry and the README fix.

What's different in this PR

The previous PRs added Bernstein to the top-of-README `Contents` table-of-contents list, which was the wrong place. This PR adds it in the right place — MCPs → Development MCPs — which is the section for MCP servers that extend Copilot's capabilities. Bernstein ships a first-class MCP server (`bernstein mcp serve`) that exposes its 37-adapter orchestrator as MCP tool calls, so it's a clean fit for that subsection.

Format follows the convention of the existing entries (single-line bullet, project link + dash + description). Description leads with what it is, mentions the GitHub Copilot CLI adapter explicitly, and avoids marketing language.

What Bernstein is

Open-source multi-agent orchestrator for CLI coding agents. Apache 2.0, Python 3.12+. Coordinates 37 cooperating CLI adapters (Claude Code, Codex CLI, Gemini CLI, GitHub Copilot CLI, Cursor, Aider, Amp, OpenHands, OpenCode, Goose, Qwen, Ollama, and 26 more) running in parallel git worktrees. The scheduler is deterministic Python — zero LLM tokens spent on coordination. Quality gates (tests, lint, types) run before merge; cost tracking with budget enforcement; plan files with depends_on for multi-stage workflows; an MCP server mode lets any MCP-compatible client drive a run.

Happy to make any framing adjustments if the entry should sit in a different subsection or read differently.

[chernistry]

Refreshed the entry: the adapter count had gone stale, and I capitalised Git so the line satisfies the awesome-lint spell-check rule. I ran markdownlint-cli2 and awesome-lint locally against the branch and the entry itself is clean; the other awesome-lint findings also appear on main without my change, so they are pre-existing.

The lint workflow needs a maintainer to approve the run before it will report on this pull request. Happy to adjust the wording if anything needs changing.