src: map UINT64_MAX to 0 in process.constrainedMemory()

When uv_get_constrained_memory() returns UINT64_MAX, it indicates
there is a constraining mechanism but no constraint is set. Per the
Node.js documentation, this should return 0 instead of exposing the
raw UINT64_MAX value to JavaScript.

Fixes: #59227

Author: crawfordxx

src/node_process_methods.cc

@@ -22,6 +22,7 @@
 #endif
 
 #include <climits>  // PATH_MAX
+#include <cstdint>  // UINT64_MAX
 #include <cstdio>
 
 #if defined(_MSC_VER)
@@ -250,6 +251,7 @@ static void MemoryUsage(const FunctionCallbackInfo<Value>& args) {
 
 static void GetConstrainedMemory(const FunctionCallbackInfo<Value>& args) {
   uint64_t value = uv_get_constrained_memory();
+  if (value == UINT64_MAX) value = 0;
   args.GetReturnValue().Set(static_cast<double>(value));
 }