Pin cargo-about through mise for license report

[romainbrenguier]

Summary

Pin cargo-about in mise.toml so the jobs already using mise-action provide the tool needed by the Rust license report task.

Verification

• Confirmed the failing jobs already run jdx/mise-action

Part of SKUNK-1662

[sonar-review-alpha]

Summary

What changed: Moved cargo-about tool management from manual CI installation to version-pinned dependency in mise.toml. The tool is no longer installed upfront in GitHub Actions workflows; instead, it's managed via mise (a version manager) with version 0.8.4 pinned. Updated documentation to reflect the new workflow where developers run mise install and the Gradle build task self-bootstraps the tool if needed.

Why: Makes the Rust license report generation self-contained and reproducible by eliminating the need for manual installation steps in CI and ensuring consistent tool versions across environments.

What reviewers should know

Key points for review:

• The Gradle task :analyzer:generateRustLicenseReport must be capable of bootstrapping cargo-about if it's missing (the logic is not visible in this diff). Verify it handles tool installation or detection gracefully.
• CI now relies on mise to provide cargo-about. Ensure developers have mise set up locally and that CI runners have it available.
• The version pinning (0.8.4) in mise.toml is the source of truth; check that this version is compatible with the project's Rust setup.
• README update clearly communicates the new prerequisite—reviewers should verify no other docs still reference the old cargo install approach.

Start reading: Look at the Gradle build logic in the analyzer module if you want to understand how the self-bootstrap mechanism works (not included in this diff).

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed for 'sonar-rust'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube