fix(node): Resolve ace_ibma.Checker is not a constructor error

[Rahul-Sivananda]

• Try to resolve the ace_ibma.Checker is not a constructor error

This PR is related to the following issue(s):

• [BUG]: Intermittent ace.Checker is not a constructor errors in Jest tests #1025

Additional information can be found here:

Currently, the generated ace-node.js file is updated multiple times when running in multiple threads, causing the ace_ibma.Checker is not a constructor error while reading it when the file is being overwritten.

This commit does the following things:

1. Read the generated ace-node.js file if it exists and create the accessibility checker without overwriting the file.
2. Throw error if there was a problem in writing the ace-node.js file instead of attempting to create the constructor from the non-existing file.

Due to the above change, we must update the generated file name.
The current file is stored as <cache-folder-name>/ace-node.js. If the cache folder is not cleared, this would cause issues when either rule archive or package version is changed, as we are no longer overwriting the file.

Suffixing rule and package version to the file name (e.g. ace-node-3.0.0-3.1.67.js) prevents this from happening.

Testing reference:

To test, run multiple accessibility tests using jest parallelly, ace_ibma.Checker is not a constructor error should not occur.
To verify that the generated file is not being overwritten, run fswatch -uvx <cache-folder-path>

I have conducted the following for this PR:

• I validated this code in Chrome and FF
• I validated this fix in my local env
• I provided details for testing
• This PR has been reviewed and is ready for test
• I understand that the title of this PR will be used for the next release notes.

[Rahul-Sivananda]

I am struggling to understand the pipeline failure reasons, and I'm unable to reproduce them locally.

For example, results for npm run wdio locally :

And npx mocha -R dot test/mocha/aChecker.Fast/aChecker.Baselines/*.test.js

Do I need to update something else for the change to work?

[Rahul-Sivananda]

I'm testing out setting the commit sha as the archive version instead of the GITHUB_REF (<pr_number>/merge). This might cause problems in packaging.

I replaced let releaseTag = (process.env.GITHUB_REF || "").substring(10); with let releaseTag = (process.env.GITHUB_REF || "").substring(10).replace("/merge", ""); this seems to be more failsafe.

[tombrunet]

Moving to #1845