downgrade Ktor to 3.2.3

[devcrocod]

• ktor 3.2.3
• Tests are ignored because Ktor 3.2.3 has issues with wasm in the test environment. However, it works outside of tests. All other targets pass these tests successfully.

Motivation and Context

compatibility with older versions of Ktor

How Has This Been Tested?

CI

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

[Copilot]

Pull Request Overview

This PR downgrades Ktor from version 3.3.1 to 3.2.3 to maintain compatibility with older versions. Due to known issues with Ktor 3.2.3's wasm/js support in test environments, several integration and transport tests have been temporarily disabled with @Ignore annotations. The tests continue to pass on all other target platforms.

Key Changes

• Ktor dependency downgraded from 3.3.1 to 3.2.3 in the version catalog
• Six tests across three test files marked as ignored with explanatory comments

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
gradle/libs.versions.toml	Downgrades Ktor version from 3.3.1 to 3.2.3
kotlin-sdk-test/src/commonTest/kotlin/io/modelcontextprotocol/kotlin/sdk/integration/WebSocketIntegrationTest.kt	Adds @Ignore annotations to three WebSocket integration tests due to wasm/js incompatibility
kotlin-sdk-test/src/commonTest/kotlin/io/modelcontextprotocol/kotlin/sdk/integration/SseIntegrationTest.kt	Adds @Ignore annotations to three SSE integration tests due to wasm/js incompatibility
kotlin-sdk-test/src/commonTest/kotlin/io/modelcontextprotocol/kotlin/sdk/client/SseTransportTest.kt	Adds @Ignore annotation to one SSE transport test due to wasm/js incompatibility

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[tiginamaria]

As I get the comment right, tests with lower ktor are failing with wasm/js, but do work with jvm. Maybe we can instead of ignoring move tests under jvm target?
Other then that looks good!

[devcrocod]

@tiginamaria Yes, I’m going to do that in the next PRs.
The WebSocket will be tested only with the JVM.

I’ll look into why sse fails with wasm and try to fix it for wasm. Otherwise, I’ll move it under the JVM as well.
At the moment, I didn’t want this to be a blocker for the release