ci(apps/client-cli): cross-platform tagged releases w/ git-cliff changelog

[xendarboh]

• https://axodotdev.github.io/cargo-dist/book/quickstart/rust.html
• https://github.com/axodotdev/cargo-dist/blob/main/book/src/reference/config.md
• https://github.com/axodotdev/cargo-dist/blob/main/book/src/ci/index.md
• install and init cargo-dist
• docs(README): add cargo dist, needed dep, how to configure projects to use it
• ci: rename workflow files to optimize organization
• follow existing releases pre-release behavior
• use git-cliff changelog

Seems cargo-dist only accepts tags of the format (v1.0.0, my-app-v1.0.0, my-app/1.0.0, ...) (not '@'). discern acceptable format, then conform other release tags to the same convention.

• update all release tags to the format <project>/<version>

Having cargo-dist use the tag as the source of version (and updating Cargo.toml in the flow) is an intractable problem (besides leaving dist's managed release.yml). So:

• docs: add Release steps including bump version

cargo binstall cargo-edit
cargo set-version -p zknet_client_cli 0.0.1-test.2`
git add . && git commit -m 'chore(client-cli): release 0.0.1-test.2'
# git push, merge to main from PR, then tag main:
git tag -s -a client-cli/0.0.1-test.2 -m 'client-cli/0.0.1-test.2'
# push tag to trigger automated release

@monodon/rust nx plugin set .cargo/config.toml:target-dir to dist/target. cargo-dist's "Create Github Release" task of host job breaks on this with error: read artifacts/dist: is a directory. So:

• rename cargo target-dir to avoid conflict.