Do an initial cargo release?

[kujeger]

Hi!

I've been porting some of my tools and apps from using reticulum-rs and/or rust-wrapped python reticulum to rsReticulum, and it's been working really great -- I'm very happy and excited about how rsReticulum is working out. Less code on my part, less bugs, and more features working!

Would you consider doing a cargo publish of some 0.0.1 (or whatever) version of how things are now, for both rsReticulum and rsLXMF? For now I've been inlcuding either local paths or pointing cargo at a specific git commit, but it's a bit awkward -- and this is already way more useful than any of the published reticulum crates on crates.io.

I imagine a rsReticulum crate that re-exports the various subcrates could be a good dev experience as well!

[drupol]

I am also looking forward to see a crate out of it, it would allow 2 things:

1. Remove the local path to rs-reticulum from this Cargo.lock file: https://github.com/ratspeak/rsLXMF/blob/main/Cargo.toml
2. Remove the postPatch section in the Nix package to fix the previous point: https://github.com/NixOS/nixpkgs/blob/1da598155d27977d91c47e51a9c84ce91f2717fd/pkgs/by-name/rs/rs-lxmf/package.nix#L22