[untested] v8(arm): use the same stack size as most other architectures

[jayaddison]

May resolve mitigate #41163.

[nodejs-github-bot]

Review requested:

• @nodejs/v8-update

[mscdex]

Changes to V8 should be made upstream.

[jayaddison]

Thanks, @mscdex - I may need to spend some more time thinking about the options before deciding whether to take this upstream; it's good to know that those are generally where V8 changes affecting Node should be applied.

In particular in this case, my understanding so far is that the reduced V8 stack sizes for ARM were introduced primarily to resolve failures in single-process, web-related use cases -- I figured that those would be less relevant for Node.

(and, as mentioned in the linked issue thread: a better solution is likely to use rlimit-based detection of appropriate stack sizes.. potentially again a topic of conversation to have with the V8 team, though)

[jayaddison]

⚠️ Although this wasn't merged, a caution for any future readers: after discussion this with the V8 development team on their v8-dev mailing list: it may currently be safe to restore the 984KB stack size for 32-bit ARM architectures, but it is not currently considered safe to do so for 64-bit ARM.