WASM: Upcoming tasks

[certik]

Original issue: https://gitlab.com/lfortran/lfortran/-/issues/761

From Zulip Chat: Building LFortran inemscripten-forge, it seems we need the following support:

• building to wasm at CI (Release type. If it works unexpectedly, we need to recompile in Debug mode and debug it.) (CI: Building LFortran to WASM #157)
• auto uploading the built lfortran.wasm && lfortran.js to https://dev.lfortran.org/ (CI: Building LFortran to WASM #157)

Also, other supports needed:

• support pow for x**2 case https://gitlab.com/lfortran/lfortran/-/issues/118 (merged)
• start with sufficient memory in the generated wasm (more details at comment, comment) https://gitlab.com/lfortran/lfortran/-/issues/126 (merged).
• passing array data from/between wasm and JavaScript
• generate the WASM "imports" based on bind(c) interfaces (https://gitlab.com/lfortran/lfortran/-/issues/771) (WASM: Support WAT for bind(c) functions #588
• drawing/visualizing the image (generated by wasm) on canvas

[Shaikh-Ubaid]

I removed runtime library and strings from the above description.

• Runtime library already has a dedicated issue at WASM: Runtime Library #555
• strings are already noted at GSoC 2022: Implementing custom WASM Backend for LFortran Roadmap #540
  • We can/might create a separate/dedicated issue for strings later

[Shaikh-Ubaid]

Please possibly review. It seems safe to close this issue.

[certik]

I think everything is fixed here, thanks @Shaikh-Ubaid.

The auto uploading of lfortran.wasm still needs some improvements, but we have a dedicated issue for that: lfortran/lcompilers_frontend#12, everything else I think is done.