Upgrade to Node LTS

[mattzcarey]

Updates node from 18 to current LTS (24) in Github CI as it is entering EOL in the new year.

Tests against both the oldest legacy version we should support until April (18) and current LTS (24).
I would strongly suggest we upgrade our oldest version to 22 soon.

Motivation and Context

How Has This Been Tested?

Tests test against both versions. We just build in the newer version so we can use tsdown. #1071

Breaking Changes

No

Types of changes

• 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

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

Additional context

[felixweinberger]

Is the NPM upgrade intentional? Apparently node 18 ships with older npm versions, might be an inadvertently breaking change?

[mattzcarey]

I thought it shipped with 10+ but yep I'm wrong. Will remove:

  {
    "version": "v18.0.0",
    "date": "2022-04-18",
    "files": [
      "aix-ppc64",
      "headers",
      "linux-arm64",
      "linux-armv7l",
      "linux-ppc64le",
      "linux-s390x",
      "linux-x64",
      "osx-arm64-tar",
      "osx-x64-pkg",
      "osx-x64-tar",
      "src",
      "win-x64-7z",
      "win-x64-exe",
      "win-x64-msi",
      "win-x64-zip"
    ],
    "npm": "8.6.0",
    "v8": "10.1.124.8",
    "uv": "1.43.0",
    "zlib": "1.2.11",
    "openssl": "3.0.2+quic",
    "modules": "108",
    "lts": false,
    "security": false
  },