chore: just specify major version to improve compatibility between dev tools

[sushichan044]

Motivation and Context

I noticed this while I was testing other issues on my end.

The 22.x.x format in .node-version was not correctly interpreted by version management tools especially mise. This PR updates the format to 22 , which is the standard notation widely supported by these tools and automatically resolves to the latest Node.js 22.x release.

Existing setup-node action in CI does not affected by this. ref

How Has This Been Tested?

Breaking Changes

Types of changes

None of them - chore patch for local dev

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation update

Checklist

• [x] I have read the MCP Documentation
• [x] My code follows the repository's style guidelines
• [x] New and existing tests pass locally
• [x] I have added appropriate error handling
• [x] I have added or updated documentation as needed

Additional context