Criteria for n-api to exit experimental status

[digitalinfinity]

At VM Summit #4, a rough criteria was formulated for n-api to exit experimental status. The consensus was that this criteria needs to be refined further, and this issue is meant to facilitate that discussion.

Current criteria:

1. • Multiple implementations of n-api on at least 2 VMs
2. • At least two modules that are NPM installable with pre-builds and all unit tests passing
3. • At least two modules used in real world use cases on at least one VM
4. • Define N-API / async_hooks dependency (Striving for a working implementation Integrate C++ AsyncHooks Embedder API with native abstraction #13254)
     (Completed with src,async_hooks,n-api: refactor async callback handling #14697)

• Version:
  v8.x

• Platform:
  All

• Subsystem:
  n-api

_{refack: enumerated the conditions, loosened condition 4 as I understand it. Also fixed number 4 link.}

[mscdex]

For those confused about the link to issue 4 in this repo, this issue is more relevant.

[refack]

@addaleax Will you be willing to release lzma-native pre-gyped as N-API (even for just a single node version)?
@gabrielschulhof we have you down for iotivity-node (I can help with pre-gyping it)

[refack]

@Silur we are looking for native-module maintainers who will release an "untagged" version built on N-API.

[addaleax]

@refack You mean, my 5k downloads/month pet project? ;) Yea, sure, it’s on my list of things to do anyway, even if just to see how smooth the transition goes.

[bnoordhuis]

I'll try to move over node-iconv next week. ~140k downloads/month with good continuous integration. (Its unwitting users! If anything breaks I usually hear about it within the hour.)

[mhdawson]

Request to move out of experimental for TSC review - nodejs/TSC#501

[vkurchatkin]

Closed by #19262