Conformance tests

[chemicL]

Add a starting setup for conformance tests

Motivation and Context

In order to comply with the recently proposed SDK tiering system, this PR starts the path to regular conformance evaluation.

How Has This Been Tested?

The current setup uses the basic building blocks that leverage the JDK HttpClient and the Servlet spec and validate the synchronous stack.

Breaking Changes

None.

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

No.

[tzolov]

LGTM,
One minor thing. Perhaps we can use logger instead of sys out in ConformanceJdkClientMcpClient.

[chemicL]

Perhaps we can use logger instead of sys out in ConformanceJdkClientMcpClient.

The use of System.out and System.err is actually intended to keep the client behaviour consistent with the way the reference implementation in Typescript behaves:

    console.log('✅ Connection closed successfully');
    console.error('❌ Error:', error);