feat(cli): sampo update command

[goulvenclech]

Add sampo update command to self-update the CLI from GitHub Releases. Only stable versions are proposed by default, use --pre to include pre-releases (alpha, beta, rc).

What has changed?

• crates/sampo/Cargo.toml: Added self_update dependency with archive and compression features.
• crates/sampo/src/cli.rs: Added Update command with --yes (skip confirmation) and --pre (include pre-releases) flags.
• crates/sampo/src/update.rs: New module that fetches releases, filters stable versions by default, and performs binary replacement.
• crates/sampo/src/version_check.rs: Switched from crates.io to GitHub Releases to align version hints with sampo update availability.
• crates/sampo/src/main.rs: Integrated update command handler and changed version hint to suggest sampo update.
• crates/sampo/src/ui.rs: Added log_info function for neutral informational messages.

How is it tested?

• crates/sampo/src/cli.rs: Unit tests for parsing sampo update and sampo update --yes.
• crates/sampo/src/update.rs: Unit tests for version parsing from tags and release filtering logic.

How is it documented?

• crates/sampo/README.md: Documented sampo update in the Commands table.

[sampo-s-bot]

🧭 Changeset detected

Merging this PR will release the following updates:

sampo (Cargo) — minor version bump

Minor changes

• Add sampo update command to self-update the CLI from GitHub Releases. By default, only stable versions are proposed, use --pre to include pre-releases (alpha, beta, rc).

[Princesseuh]

Looks fine. I don't know the self-update crate so I can't tell if it has specific needs or anything. Some other tools call this command self-update instead which might be worth it to avoid conflicting with a future command, not sure

[goulvenclech]

Looks fine. I don't know the self-update crate so I can't tell if it has specific needs or anything. Some other tools call this command self-update instead which might be worth it to avoid conflicting with a future command, not sure.

Thanks for bringing that up but, after thinking through it, I still prefer update. It’s more intuitive and easier to remember, even if I agree it’s a bit less explicit.

Also, I don’t expect it to clash with a future command, we generally use « bump » / « version bump » for versioning « update ».