util: don't set the prototype of callbackified functions

Using `util.callbackify()` should not set the prototype for the
returned function to the one from the input function. It could cause
confusion while debugging otherwise.

PR-URL: #26893
Fixes: #26890
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Jeremiah Senkpiel <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>

Author: BridgeAR

lib/util.js

@@ -194,7 +194,6 @@ function callbackify(original) {
             (rej) => process.nextTick(callbackifyOnRejected, rej, cb));
   }
 
-  Object.setPrototypeOf(callbackified, Object.getPrototypeOf(original));
   const descriptors = Object.getOwnPropertyDescriptors(original);
   // It is possible to manipulate a functions `length` or `name` property. This
   // guards against the manipulation.

test/parallel/test-util-callbackify.js

@@ -157,6 +157,11 @@ const values = [
 
     const cbAsyncFn = callbackify(asyncFn);
     assert.strictEqual(cbAsyncFn.length, 2);
+    assert.notStrictEqual(
+      Object.getPrototypeOf(cbAsyncFn),
+      Object.getPrototypeOf(asyncFn)
+    );
+    assert.strictEqual(Object.getPrototypeOf(cbAsyncFn), Function.prototype);
     cbAsyncFn(value, common.mustCall((err, ret) => {
       assert.ifError(err);
       assert.strictEqual(ret, value);