Building artifacts when imported, without including in repo

[mattyg]

There is a complex set of dependencies for building the output packages. In the short term it may make sense to just include artifacts in the repo, but this should be replaced with a build setup.

Building tauri-plugin-holochain-service cargo package

• Build rust package holochain_runtime
• Build rust package holochain_runtime_uniffi
• Use cargo-ndk to build holochain_runtime_uniffi for all android targets, copy .so to jniLibs in tauri-plugin-holochain-service
• Use uniffi to generate kotlin bindings for holochain_runtime_uniffi, copy to to tauri-plugin-holochain-service (See Extract uniffi bindings, aidl interface and aidl types into shared kotlin package #12)
• Build the holochain-env js script with pnpm run build:js:holochain-env && rollup -c (this may not be needed in this package, see Multiple binders on HolochainService: admin & app #3)

Building tauri-plugin-holochain-service-consumer cargo package

• Build rust package holochain_runtime
• Build rust package holochain_runtime_uniffi
• Use uniffi to generate kotlin bindings for holochain_runtime_uniffi, copy to to tauri-plugin-holochain-service-consumer (See Extract uniffi bindings, aidl interface and aidl types into shared kotlin package #12)
• Build the holochain-env js script with pnpm run build:js:holochain-env && rollup -c

Building tauri-plugin-holochain-service-api js package

• Build the tauri-commands js package with pnpm run build:js:tauri-commands:es && rollup -c

Building tauri-plugin-holochain-service-consumer-api js package

• Build the tauri-commands js package with pnpm run build:js:tauri-commands:es && rollup -c