test: use --max-opt=0 instead of --no-opt test-linux-perf.js

[joyeecheung]

--no-opt only disables turbofan but other compilers may still be enabled, in that case we may not be able to find the interpreted frames if the function is compiled soon enough. Instead use --max-opt=0 which turns off all compilers.

Refs: #48861

[nodejs-github-bot]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2204-intel-64,v8test=v8test/5471/

[nodejs-github-bot]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2204-intel-64,v8test=v8test/5473/

[joyeecheung]

hmm, so the test is still failing, I took a look at the logs again and I think --interpreted-frames-native-stack is actually broken - it was a bit confusing because the test concats the outputs together before testing them, so there are still compiled functions that you can see in the second part of the output, but if you check out the first part of the concatenated output, it's actually all "unknown".

[joyeecheung]

Although from local testing, I am able to get the interpreted names alright, so it might have something to do with the benchmark machine setup?

[joyeecheung]

I think this is not the right approach, because even --max-opt=0 doesn't ensure that V8 won't compile of our target functions (with the baseline compiler), it's completely up to V8 whether it wants to interpret or compile a function...though there might be some other tricks to force V8 interpret one (e.g. making it super big?)