Tauri Bundling & Updating

1. There is the @guijs/server-core which we will build and ship as a sideloaded node app in the binary space of the tauri bundle for MacOS, Linux (arch, rpm, deb, ubuntu), Windows 10 - we won't ship the node binary, expecting that the dev has it installed in their $path.

2. There is the @guijs/frontend-core which we will build and ship as the HTML/JS/CSS app in the tauri binarys space using the no-server methodology.

3. Ideally, the "first run" of the binary would do some system analysis and if the specs aren't met, then enquire if the user wants the binary to drop to an internal shell and install nodejs with nvm etc - or if it should close and let the user do that themselves.

4. Publishing an app will be made with GH Actions using the matrix like at Tauri. All node modules will be hosted at NPM - but we can build the tauri app from source.

5. Updating will be done via GH artifact download.

Todo List:
- [x] icon creation with tauricon
- [x] app.js and deps bundled into sideloader space (consider compression options)
- [x] build of the frontend, transpilation for `no-server` drop into app-binary
- [x] first run "wizard" and API hooks with platform and dependency detection
- [x] CI build pipeline with "release" strategy
- [ ] updater (will require a number of utility releases to get right. probably 5-10)