feat(wasm-as): codegen should create IModule interface

[Niraj-Kamdar]

• Closes: Wasm-as wrapper developers extend & implement IModule interface from wrap codegen #1458

Changelog

Features

• Codegen for wasm wrappers now generates ModuleBase class that can be extended by wrap dev

Future work

This PR only changes devx for wrapper development for the Assemblyscript wrapper. Rust wrapper will be covered in the following PR #1464

[dOrgJelli]

This looks great! Added a few improvements I think could help.

[Niraj-Kamdar]

@cbrzn sorry for overwriting your commits. I got some git issues and wasn't able to fix it without force pushing.

[dOrgJelli]

I'm very eager to get these changes merged, it looks amazing.

I want to make sure we give users a seamless experience and options to go back to the legacy codegen if desired: https://github.com/polywrap/toolchain/blob/dorgjelli/binding-import/vision.md

[dOrgJelli]

I suppose

I'm very eager to get these changes merged, it looks amazing.

I want to make sure we give users a seamless experience and options to go back to the legacy codegen if desired: https://github.com/polywrap/toolchain/blob/dorgjelli/binding-import/vision.md

I suppose we could do this "legacy support" and the decoupling of the binding projects from the toolchain repo in another PR right after this one, thoughts @Niraj-Kamdar?

[Niraj-Kamdar]

https://github.com/polywrap/toolchain/blob/dorgjelli/binding-import/vision.md

It makes sense to me! And yes separate PR would be better. I don't want to make this one more monstrous than it already is!