Introduce SNAPSHOT releases

[StefMa]

Is your feature request related to a problem? Please describe.
Since the library will probably change quite often in the foreseen future, consumers have to wait until a "full" release happen, before they can use the latest and greatest.

Describe the solution you'd like
I do like to see SNAPSHOT releases.
Each time something is merged to main, a new SNAPSHOT release should be published to the publishing portal.
See https://central.sonatype.org/publish/publish-portal-snapshots/

Describe alternatives you've considered
Alternatively jitpack.io could be used.
But since 0.0.5 already failing (https://jitpack.io/#modelcontextprotocol/kotlin-sdk), and I'm not even aware of they can build iOS targets, I wouldn't consider this as a "real" alternative

Additional context
E.g. people waiting for a release for iOS (#81 (comment)).
People discover bugs earlier than later #105
... 🤷
I guess its just a best practise, no? 😁

[devcrocod]

In my opinion, the problem is that we haven’t been releasing sdk regularly

Right now, our plan is to update sdk with the latest specification, and I think we should start releasing patch versions with fixes instead of using snapshots

[StefMa]

What does regularly mean? 🫣
Does every bug fix lead to a new patch release?
How do you consider if a bug is a patch release worthy?
When do you plan to create a minor release? Only if the specification changes anything? Of already if a few contributions happening that might touch code style only..?!

It might work out.
But I guess it also doesn't hurt anyone to push snapshots on each merge to main. 🤷‍♂️

Everyone in the maven-universe is aware of how snapshots behave and know the risks while enjoying the benefits of working on the bleeding edge.
Since mcp is "quite new" and the AI race is still running, I think it's worth to provide a bleeding edge mcp sdk.