benchmark: add benchmark utility for isNativeError function

[mertcanaltin]

added benchmark code for isNativeError function

for: #60468 (comment)

➜  node git:(mert/create/benchmark/isNativeError) ✗ ./node benchmark/util/is-native-error.js
util/is-native-error.js n=1000000 version="native" argument="true": 320,881,319.7977036
util/is-native-error.js n=1000000 version="js" argument="true": 260,824,204.4861763
util/is-native-error.js n=1000000 version="native" argument="falsePrimitive": 338,562,200.81681514
util/is-native-error.js n=1000000 version="js" argument="falsePrimitive": 341,525,155.71839476
util/is-native-error.js n=1000000 version="native" argument="falseObject": 320,414,334.1838198
util/is-native-error.js n=1000000 version="js" argument="falseObject": 316,143,054.73226637

[nodejs-github-bot]

Review requested:

• @nodejs/performance

[RafaelGSS]

I'm not confident about how useful this benchmark is

[RafaelGSS]

This is likely being optimized.

[mertcanaltin]

Hi, I tried to fix this by using more arguments and variable arguments. 5fcf423

[anonrig]

I'm not confident about how useful this benchmark is

Any recommendations?

[lpinca]

Any reason for this? If I'm reading correctly, the elements are all equals.

[mertcanaltin]

I wanted to provide more arguments.

[lpinca]

With

const testArg = testArgs[iteration % 3];
func(testArg)

below, I'm still not sure I understand.

[mertcanaltin]

You're right, it could be misleading for them all to be the same I changed them with different arguments.
9de3f6f

now "%3" alternative I use testArgs.length

[mertcanaltin]

After the latest changes, I got a test failure because the benchmark was running with three configurations instead of the expected one or two. I’ve updated the code so each run uses only a single argument, matching the test infrastructure’s requirements. FYİ @RafaelGSS