Align MCP package manifest version

[haochencheng]

Summary

• Align package.json and package-lock.json to 0.1.7 so they match server.json.
• Unblocks the Growing MCP release runner, which fails closed when package and server manifest versions diverge.

Safety / Review Notes

• Manifest-only change; runtime code is unchanged.
• Required for Remote MCP production deployment of the Glama well-known verification endpoint.

Validation

• npm run release:readiness

[haochencheng]

This PR is blocking the next Remote MCP production deploy through the Growing MCP release bridge.

Current live facts checked on 2026-06-10:

• https://mcp.synapse-network.ai/readyz returns 200.
• https://mcp.synapse-network.ai/.well-known/glama.json still returns 404, so PR Add Glama connector verification metadata #34 has not reached prod yet.
• npm latest for @synapse-network-ai/mcp-server is still 0.1.5.
• Official MCP Registry latest metadata is 0.1.7 with package artifact 0.1.5.
• The Growing MCP runner failed closed for release id 3 because source manifests diverged: package manifest 0.1.5, server.json.version 0.1.7.

After this merges, the next deploy step is to update local main, create a fresh MCP release ledger for the merged commit, and run the prod-only Remote MCP bridge until /.well-known/glama.json is live.