Update & fix nodejs data for Crypto

[skyclouds2001]

Summary

The support for the Web Crypto API is:

in v15.0.0, the API has been shipped, but can't access globally, access via the crypto module with the alternative name webcrypto via nodejs/node#35093

in v17.6.0, v16.15.0, the API can be available to global context, but need to be enabled with --experimental-global-webcrypto CLI flag via nodejs/node#41938

in v19.0.0, the API is available to global context without flags, but can be disabled with --no-experimental-global-webcrypto CLI flag via nodejs/node#42083

in v23.0.0, the API is marked as not experimental via nodejs/node#52564

See also:

https://nodejs.org/docs/latest/api/globals.html#crypto
https://nodejs.org/docs/latest/api/webcrypto.html#class-crypto
https://nodejs.org/docs/latest/api/crypto.html#cryptorandomuuidoptions
https://nodejs.org/docs/latest/api/crypto.html#cryptogetrandomvaluestypedarray

Also fixes #23784

Also note that the fix in #21414 and the test in #20752 is not correct, as the issue and PR use the link of the getRandomValues() method of crypto module (which says v17.4.0), NOT the getRandomValues() method of Web Crypto API (which says v15.0.0). Also notice that, the getRandomValues() method of crypto module is simply a convenient alias of the getRandomValues() method of Web Crypto API

Test results and supporting details

Related issues

[caugner]

This doesn't look right: Since the parent feature is only available via the crypto module from 15.0.0, and only outside of the crypto module from 19.0.0, isn't this note obsolete, and the current support statement (17.4.0) is correct?

Suggested change

	"version_added": "15.0.0",
	"notes": "Since v17.4.0, a similar method is available via the <code>crypto</code> module."
	"version_added": "17.4.0"

[skyclouds2001]

the v17.4.0 one means require('crypto').getRandomValues(), see https://nodejs.org/docs/latest/api/crypto.html#cryptogetrandomvaluestypedarray
the v15.0.0 one means require('crypto').webcrypto.getRandomValues(), see https://nodejs.org/docs/latest/api/webcrypto.html#cryptogetrandomvaluestypedarray
per documentation, the v17.4.0 one is simply an alias of the v15.0.0 one
also, since here is referring Crypto interface's getRandomValues(), the v15.0.0 should be used instead

[caugner]

Why don't we keep the "version_added": "19.0.0" entry?

[skyclouds2001]

because there is no difference made to randomUUID() before v19.0.0 and after v19.0.0 (while the Crypto interface is exposed to global scope, so just combine the previous two entries)