util: eliminate unecessary internal/util export

[jasnell]

The objectToString method was only being used in one place
within internalUtil. It didn't make sense to have it as
a separate exported mnethod.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

internal util

[jasnell]

CI: https://ci.nodejs.org/job/node-test-pull-request/6491/

[targos]

#11128 uses objectToString

[jasnell]

hmm... could it not simply define it's own objectToString or use Object.prototype.toString() directly?

[jasnell]

(thanks for pointing that out, btw :-) ...)

[targos]

could it not simply define it's own objectToString or use Object.prototype.toString() directly

absolutely. /cc @joyeecheung

[targos]

LGTM this function doesn't add much value

[joyeecheung]

The reason to use objectToString is in #10282 (comment) , the util can do the caching part at startup(or even get the untampered with version through bindings)

[jasnell]

hmm... I'll hold on this then. I've been thinking through a solution on trapping the instances of classes we depend on. I'll see if I can get that PR in later this week.

[jasnell]

I'm going to go ahead and close this without further action. There are other places where this function is looking to be used.