console.error pollution logs removed in tests

[davolokh]

console.error mocked in tests (only locally where it's needed) to keep logs clear

Motivation and Context

In current state when tests run there are several console.error prints which are signs of normal behaviour, but add additional noise and require careful checks ("green -- good" approach is not applicable). Mocking console.error allows to keep logs clear (and if logs are clear ANY new information is visible, can't be lost in other logs and chances that it would be treated properly are higher.
There is possibility to mock console.error globally (in jest.config.js), but IMO it could be potentially harmful (hides all error by default).

How Has This Been Tested?

Tests themselves are fixed.

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

before:

after: