Added support for ES Modules in p5.js-web-editor

[takshittt]

Fixes #3304

Changes: Implemented support for import/export ESM standard modules.

Description:

This pull request adds support for import/export ESM (ECMAScript Modules) standard modules.

I have verified that this pull request:

• [yes ] has no linting errors (npm run lint)
• [ yes] has no test errors (npm run test)
• [ yes] is from a uniquely-named feature branch and is up to date with the develop branch.
• [yes ] is descriptively named and links to an issue number, i.e. Fixes #3304

[welcome]

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

[dipamsen]

This is an interesting idea.

I do think supporting ES Modules is a good idea since modules it is a perfectly valid way to write a p5 sketch, and sometimes has advantages over traditional scripts. However, I believe this is not how most users use/will use p5.js, due to many reasons: most p5.js tutorials use scripts instead of modules; p5.js itself is a UMD library - it doesn't expose a ESM distribution (by nature, it will be very hard if not impossible for it to do so).

I have the following questions:

1. Is it needed to have duplicated option for 'New Project' just for projects using ES Modules? I think someone who wants to use ESM to write their code has the know-how to change 3 lines of code from the default starter sketch, to get a 'ESM project'. I don't think this feature has enough benefit, but instead may be confusing to beginners.
2. Your isModule check should just be from whether it is linked as type="module" or not, checking whether import or export exists is a weak condition to know whether a file is a module. (eg. the word may match within comments and strings, or in a module there may be no imports or exports)
3. does this work on all types of imports and exports? (ref: import, export)
4. Does it suffice to just replace the import path with the blob url? If so, a lot of code duplication can be removed.