tools: expose v8 fast-calls header to native addons

[Aditi-1400]

Fixes #52923

This wasn't exposed initially because the V8 team objected to it as it wasn't stable enough.
If everything is stable now, it should be fine to do so now?

[anonrig]

cc @nodejs/tsc @nodejs/v8

[targos]

It's not stable. I had to make substantial changes to our internal use of the API in #57114

[anonrig]

Blocking due to #57574 (comment)

[joyeecheung]

I had to make substantial changes to our internal use of the API

I think that can be said about many APIs we use from V8 for every V8 upgrade? Even String::Value, which we've been using for I-dont-how-long, were recently deprecated, but I wouldn't call that API unstable. I think it's expected that even very stable APIs can get breaking change in a major V8 upgrade. But since we don't do major V8 upgrade within a major release anyways, that's not really an issue, and having to fix things up for new major release of Node.js is also expected for addons (especially if they use raw V8 APIs).

cc @gahaas who's been doing some deprecation of the fast call API...should it be considered stable enough to allow Node.js addons to use the fast call APIs?

[gahaas]

Chances are that the fast call API will still change a bit this year.

[jasnell]

+1 to holding off. This is still a bit too premature.

[targos]

we don't do major V8 upgrade within a major release anyways

We haven't done that recently because there are too many build issues and V8 versions are not bumped regularly. I hope that we'll be able to do major upgrades again in the future.