Make Example MCP Name consistent

[C-Ross]

Summary

Makes the MCP server name consistent in the example block.

Why

Ease of use only, Nit.

What changed

• GItHub enterprise config example.

MCP impact

• No tool or API changes
• Tool schema or behavior changed
• New tool added

Example only.

Prompts tested (tool changes only)

• N/A

Security / limits

• No security or limits impact
• Auth / permissions considered
• Data exposure, filtering, or token/size limits considered

Tool renaming

• I am renaming tools as part of this PR (e.g. a part of a consolidation effort)
  • I have added the new tool aliases in deprecated_tool_aliases.go
• I am not renaming tools as part of this PR

Note: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.

Lint & tests

• Linted locally with ./script/lint
• Tested locally with ./script/test

Docs

• Not needed
• Updated (README / docs / examples)

[Copilot]

Pull request overview

This PR makes the MCP server naming consistent in the GitHub Enterprise configuration example by changing the server key from "proxima-github" to "github-octocorp". This improves documentation clarity by aligning the server name with the example organization "octocorp" used in the URLs, following the established naming pattern where the main service uses "github" and enterprise instances use "github-{organization}".

Changes:

• Updated GitHub Enterprise Cloud data residency example to use "github-octocorp" instead of "proxima-github" as the server key