just_ppe

I'm still having issues with tinygo and easyjson. Trying to build the example from this issue (go 1.17) ends up with ``` tinygo build -o test main.go Undefined symbols for...

I've briefly reviewed the PR and I really like the implementation. The only thing that bothers me is the c/p of the rust-wasm-imports..it will be a bit painful to maintain...

1. I believe the Go and AS will be removed in the near future - there's exactly ZERO interest in the community in writing contracts in those languages (plus both...

ad. 2 - this should be done/refactored within a separate issue.

https://github.com/warp-contracts/warp/issues/309, @rpiszczatowski will try to refactor this crap :-)

@noomly , I believe we could merge this PR as is...the only thing missing is an integration test for the new format... sth similar to https://github.com/warp-contracts/warp/blob/main/src/__tests__/integration/wasm/rust-deploy-write-read.test.ts

> hey @ppedziwiatr , I'll be back from vacation on the 9th, I'll be able to add the tests then. no rush :-)

btw. @noomly I've released the `1.2.48-beta.1` of the internal writes refactor (https://github.com/warp-contracts/warp/pull/311) - which is a prerequisite to a more advanced optimization for WASM (like reusing the handlers, instead of...

> What do you think? Should we make it an optional field that defaults to JSON or should we leave it as a required field? We can't break backwards compatibility...

@rpiszczatowski we need to return to this :-)