Testing the new artoolkit5-js with Allow Memory Growth

[kalwalt]

⚠️ All PRs have to be done versus 'dev' branch, so be aware of that, or we'll close your issue ⚠️

What kind of change does this PR introduce?

This is a bugfix, i am experimenting with the ES6 feature dev branch.

Can it be referenced to an Issue? If so what is the issue # ?
See issue #357 and AR-js-org/artoolkit5-js#11

How can we test it?

Test the examples in the aframe and three.js folder, in particular nft examples are much affected

Summary

Sometimes running the examples (ES6 feature in dev branch) with a Mobile device i get a out of Memory issue as described in AR-js-org/artoolkit5-js#11 this occur especailly with the NFT examples.

Does this PR introduce a breaking change?
Not to the final user. Changes occur internally arjs-context.js and the different artooolkit5-js package.

Please TEST your PR before proposing it. Specify here what device you have used for tests, version of OS and version of Browser
Tested with:

• Oppo A72 running Android 11.1 and Chrome 95.
• Wiko View running Android 7.1.2 Chrome 95.0.4638.74 .

Other information
This issue occurs only in Mobile devices.
This PR also remove the double artoolkit init in the Context class and in the worker. This is not necesssary because we init artoolkit already in the ARController _initialize https://github.com/AR-js-org/artoolkit5-js/blob/aa21c379d51b08e9a0d52b26f9f6928084ddb844/src/ARController.js#L1260

task to complete

• make other tests
• publish the new artoolkit5-js package and change the ref in AR.js package.json see Fix out of memory issue artoolkit5-js#12
• restore old build path in nft examples

[kalwalt]

I need to test also with another Mobile device, but i think this should solve the issue.