Add versioning and releases for Cyware MCP server

[glenn-sq]

Is your feature request related to a problem? Please describe.
Currently, the project does not provide tagged versions or official releases. This makes it difficult to pin to a stable version of the code. Without versioning, updates to the main branch can introduce breaking changes unexpectedly, which creates friction when integrating the MCP repo into production workflows

Describe the solution you'd like
I would like the project to adopt semantic versioning (or a similar scheme) and begin tagging releases. Publishing GitHub releases would make it possible to:

• Pin to a known working version.
• Upgrade with confidence by reviewing release notes.
• Ensure compatibility across environments without unexpected regressions.

Describe alternatives you've considered

• Pinning to specific commits: This is possible but not ideal, since commit hashes are less clear, harder to track, and don’t convey stability or intended compatibility.
• Maintaining a fork: This would add overhead and drift from the upstream repo.
• YOLO'ing and just using the latest

Additional context
Having official versions and releases would align with common best practices for open-source projects, improve reliability for users, and make the MCP repo easier to integrate into automated systems (e.g., package managers, CI/CD pipelines).

[harsh-shukla-cyware]

Hi Glenn, for sure we will add and maintain the releases.