remove logging capability from MCP server

[Vishnuujain]

Describe your changes:

Fixes #26152

Because we use a stateless HTTP architecture for our MCP server, we physically cannot support MCP's push-based logging notifications (which require a persistent connection like SSE or WebSockets). The underlying Java SDK (McpStatelessAsyncServer) doesn't even have a handler for logging/setLevel in stateless mode, which is exactly why VSCode is throwing that error.

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[gitar-bot]

Code Review ✅ Approved

Removes unimplemented logging capability from MCP server to clean up unused code. No issues found.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[github-actions]

Changes have been cherry-picked to the 1.12.2 branch.