bindings init

[krisbitney]

TODO:

• Add CD that pushes build artifacts to github

Includes:

• app-typescript
• plugin-typescript
• plugin-rust
• plugin-python
• plugin-kotlin
• wrap-assemblyscript
• wrap-rust

The wrap/rust bindings will come in a future PR. See #5

Closes polywrap/kotlin-client#31

Notes

The wrap-assemblyscript bindings have a spacing/indentation issue that I'm fairly sure is an artifact of the handlebars package. The spacing becomes distorted when partials reference other partials.

The plugin-kotlin bindings use a serialized version of the wrap manifest in order to avoid adding a JSON dependency to the Kotlin client. The manifest bytes output from the wrapper bindings do not match the expected CLI output. MessagePack serialization output can vary depending on the configuration of the MessagePack library used, so this is not necessarily an issue. For example, some libraries can code an i32 as an i16 to save space. The manifest bytes in the bindings are fine so long as the Rust client's MessagePack serialization package follows the MessagePack standard.

[Niraj-Kamdar]

LGTM! I left some small comments and few improvements that came to my mind! Some of those can be done in subsequent PR. I agree that rust crates for common functions and utility can be nice to have to improve readability of the repo.