Add crates.io release workflow, crate READMEs and LICENSE

[setoelkahfi]

What

• release-crates.yml: on a v*.*.* tag (or manual dispatch), checks the tag against the workspace version, runs fmt, clippy, tests and the lower-crate solo builds, then publishes core, aso, pricing, signing, reports, frontend, mcp and cli to crates.io in that order. Publishing uses trusted publishing (OIDC), so there is no registry token secret. Versions already on crates.io are skipped, so a re-run resumes after a partial failure. Once everything is published it dispatches release-github.yml and release-mcp-registry.yml with the same tag.
• A README.md for each library crate, referenced from its Cargo.toml via readme.
• The Apache-2.0 LICENSE at the repo root.
• Copyright holder changed from Splitfire AB to PT Sigit Mitra Bangun in the READMEs and two doc-comment examples. The 5mb.app link is gone.
• The root README said seven crates and left out reports. It now lists all eight.

Before the first release

• Each of the eight crates needs a trusted publisher on crates.io pointing at smbcloudXYZ/smbcloud-ascapi and workflow release-crates.yml. The publish job runs in the crates-io environment, so the crates.io config must match if it names one.
• The new READMEs change the package contents, so the next release needs a version bump (the tag check enforces this). 0.1.1 is already published and can't be replaced.
• LICENSE sits at the repo root, so it is not included in the published crates. Each crate still declares Apache-2.0 in its metadata.

Checked

cargo fmt --check, cargo check --workspace --locked and cargo doc with -D warnings pass locally. The workflow has not run yet.

[sigit-code-review]

This change introduces a new GitHub Actions workflow (release-crates.yml) to automate publishing all workspace crates to crates.io in dependency order, with trusted publishing (OIDC) and robust handling of partial failures. Each library crate now has a README.md referenced in its Cargo.toml, and the root README is updated to list all eight crates, including reports. The Apache-2.0 LICENSE is added at the repo root. Copyright and example references are updated from Splitfire AB to PT Sigit Mitra Bangun. The workflow ensures the tag matches the workspace version, runs formatting, lint, and tests, and triggers further distribution workflows after a successful publish. No critical or warning issues are present in the diff.

---

Automated review by siGit Code Review · commit 431924d · see the review dashboard