Introduce Kotlin client/server <--> TypeScript client/server integration tests

[skarpovdev]

General requirement to run the tests (apart from the main requirements for running any code in the repo) is to have node.js installed. I don't see the need for a separate README.md, but let me know if you think it's needed.

1. In setupTypeScriptSdk we clone the latest head of TypeScript SDK and instal all the dependencies. I thought about using the released version by installing it with npm, but decided to run tests with the latest commits to help us find issues faster, before the new version is released.
2. I put edge cases coverage into separate test classes to keep the main integration tests easy to find and debug. Btw, this part is mostly done by Junie.
3. For TypeScript server I use simpleStreamableHttp from examples. If there is a concern it will be changed and hence such usage better be avoided, it can easily be migrated into a separate file. DONE ✅
4. Kotlin server is a custom implementation to allow for more thorough testing, pls take a closer look at it.

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

[devcrocod]

@skarpovdev please take a look at a validation check

[skarpovdev]

@skarpovdev please take a look at a validation check

@devcrocod The test fails only in this branch because this is the only place where we actually run jvm tests that rely on JUnit 5. I fixed it along with the bug in #243

[devcrocod]

lgtm