src,lib: move things away from util binding

[juanarbol]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[juanarbol]

Ref: #30884

[addaleax]

@juanarbol I’d definitely prefer making changes to process.binding() in JS land over making changes to the C++ level – otherwise we’ll just end up moving all of our code inside the C++ code base around from one binding to another. So what I’d have in mind is modifying process.binding() to return modified binding objects for an argument like util?

[juanarbol]

Aaaah, I get it, so, the C++ binding (node_util.cc) shouldn't change, just wrap some of that C++ API to a different JS module, am I right?

[addaleax]

@juanarbol Changing only process.binding() in JS is what I’d prefer, yes 👍

[juanarbol]

Do you have any suggestion or a list of methods to be migrated?

[addaleax]

@juanarbol I’m not sure – it’s really tricky figuring out where each native binding method stands in terms of userland usage. That’s part of why we should mvoe away from it, though :) For now, how about only providing the functions on process.binding('util'), and leave out the constants and maybe setHiddenValue/getHiddenValue? That’s kind of a small step but it might be good for getting us started.