test: change WPT status files into CommonJS files

[panva]

This PR updates the WPT status files to be .js files.

The motivation for this change is to be able to use the javascript syntax to minimize the likelyhood of conflicts when adding/removing expectations and to allow for comments to be added for test blocks that may be failing for a specificic reason.

This would also allow to make more failures optional depending on config rather than current workaround being flaky, e.g. the console expectations file could be:

'use strict'; const hasCrypto = Boolean(process.versions.openssl); const hasIntl = !!process.config.variables.v8_enable_i18n_support; const idlharnessFailures = [ ]; if (!hasCrypto || !hasIntl) { idlharnessFailures.push( // https://github.com/nodejs/node/issues/44185#issuecomment-1219388742 'console namespace: operation assert(optional boolean, any...)', 'console namespace: operation table(optional any, optional sequence<DOMString>)', 'console namespace: operation dir(optional any, optional object?)'); } module.exports = { 'idlharness.any.js': { fail: { expected: idlharnessFailures, }, }, };

The linter is configured to support that (newline for every array element, newline for array brackets). max-len is disabled because we cannot control the length of WPT test names and want them to fit on a single line.

[panva]

I've also considered yaml or json5 but felt CJS is more at home here and the present js linter can maintain the status files better.

[panva]

I will deal with merge conflicts when landing this.

[panva]

cc @nodejs/testing

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/48713/

[joyeecheung]

RSLGTM with a nit.

[panva]

actually, not going to bother atm with ideas around the WPTRunner still in flight