Closing in on a usable release

[andrewdavidmackenzie]

Recently, I have been making quite a few changes related to how the project is built and published and released, to make it more rust standard, and hopefully will be easier for others to consume.

I now have a simplified build with fewer cross dependencies between crates that need to be handled manually.

I have a working release workflow at last for the workspace, using "cargo release" that tags, compiles, builds assets and prepares the release in GH.

I have converted all my "sample" flows to be examples of flowr, and they are build and tested with every build.

I have improved how the flowstdlib is build, and then compiled to wasm. I have a few changes remaining here to simplify more.

Remaining work in this area is more or less:

• Stop flowstdlib producing a binary (that builds the wasm), just build the wasm using flowc directly.
• Then I can stop releasing assets to flowstdlib, it will continue to be a dependency of flowr runners for the native implementation
• I want to then upload the wasm cross-platform compiled version of flowstdlib as an asset to GitHub
• Then maybe I can even get brew install to work, installing working binaries (for flowc, flowrcli, flowrex, flowrgui) and the wasm version of flowstdlib!

Then I would do a 1.0 release I think!!