`copilot` should notify the user of a disabled MCP server on startup

[andyfeller]

Describe the bug

When invoking copilot using the --disable-mcp-server flag, it is unclear whether the indicated MCP server is actually disabled based on the start up messages. It would be helpful to indicate some way both configured and enabled MCP servers.

Affected version

0.0.355

Steps to reproduce the behavior

1. Setup MCP server
2. Invoke copilot --disable-mcp-server <SERVER NAME>

Expected behavior

No response

Additional context

No response