util: fix util.inspect with proxied function

[starkwang]

Fixes: #25212

Checklist

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

[nodejs-github-bot]

@starkwang build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/2083/pipeline

[BridgeAR]

It does not hurt to do this but it will not solve the overall issue with proxies: they are difficult to reason with and even more difficult to write in a way that does not interfere with things.

We trigger multiple traps while inspecting an object and we can not work around all of the issues that might potentially come up.

Another example that would fail is using an empty array instead of the function.

[bnoordhuis]

LGTM. I agree with Ruben's comment but this PR is still an improvement over the status quo so why not?

[starkwang]

We trigger multiple traps while inspecting an object and we can not work around all of the issues that might potentially come up.

@BridgeAR Agreed. We can not fix all these issues. For example, an array with a weird proxy is hard to fix.

But at least we can make it a little better :-)

[starkwang]

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

[addaleax]

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

[addaleax]

Landed in 6c7c77e