fix(vercel): clamp runtime config to valid node versions

[cjpearson]

🔗 Linked issue

#2819

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This change ensures that only supported node versions will be used as the default runtime value for the vercel preset. If a non-LTS version of node is used, it will use the previous LTS. If the version is outside the range supported by vercel, it will be clamped to the min/max of the supported range.

The runtime value can still be manually overridden as needed.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

I think instead we can use an array of supported Node.js versions in vercel and clamp (up) to closest

[cjpearson]

Are you thinking something like this?

  let usedNodeVersion = 0;
  for (const version of SUPPORTED_NODE_VERSIONS) {
    if (Math.abs(systemNodeVersion - version) <= Math.abs(systemNodeVersion - usedNodeVersion)) {
      usedNodeVersion = version
    }
  }

[pi0]

Something like this could be nice 👍🏼 I think if SUPPORTED_NODE_VERSIONS is sorted array, we can find first upper abound with simple find as well.