fix: sync package.runtime.json to match package.json version 2.22.4

Addresses version desynchronization that caused release workflow failures.
The package.runtime.json was stuck at 2.22.0 while package.json advanced to 2.22.3,
preventing npm package publication since v2.21.1.

Changes:
- Bump package.json to 2.22.4
- Update package.runtime.json to 2.22.4 via sync script
- Ensures release workflow will properly detect version change

This fix will allow the automated release workflow to publish v2.22.4 to npm
and create the corresponding GitHub release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Conceived by Romuald Członkowski - www.aiadvisors.pl/en

package.json

@@ -1,6 +1,6 @@
 {
   "name": "n8n-mcp",
-  "version": "2.22.3",
+  "version": "2.22.4",
   "description": "Integration between n8n workflow automation and Model Context Protocol (MCP)",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package.runtime.json

@@ -1,6 +1,6 @@
 {
   "name": "n8n-mcp-runtime",
-  "version": "2.22.0",
+  "version": "2.22.4",
   "description": "n8n MCP Server Runtime Dependencies Only",
   "private": true,
   "dependencies": {