test/parallel/test-tick-processor-arguments fails on SmartOS with V8 >=11.8

[targos]

I think disabling that test on SmartOS is an expedient solution for now. I took a look at fixing the test on SmartOS, but patching the V8 tooling to support BigInt for that test case just broke the many other parts of V8 that currently rely on parseInt behaviour.

I've raised https://bugs.chromium.org/p/chromium/issues/detail?id=1486517 with the V8 team to see if they have any useful input, but the proper fix for this looks like a reasonable amount of work that doesn't feel like it should be our responsibility to fix, and given the amount of parseInt hardcoding currently in the V8 tools and the fact they deliberately only have partial BigInt support I don't know that our work on a fix would even be accepted upstream.

As I mentioned in the other bug, node itself appears to work absolutely fine with the V8 merges, it's just this single test case with a clear bug in the V8 tooling scripts, so while not ideal I don't think it should hold up this merge, especially as the number of SmartOS users who use V8 log parsers is probably at or close to zero ;-)

Originally posted by @jperkin in #49639 (comment)

[joyeecheung]

I think disabling that test on SmartOS is an expedient solution for now.

SGTM