Google Workspace CLI: matoleo yote na matoleo ya zamani

What's Changed
- ci: pin cross-rs to v0.2.5 in release workflow by @jpoehnelt in #651
- fix: verify SHA256 checksum in npm postinstall script by @jpoehnelt in #650
- ci: add cargo-audit workflow for dependency vulnerability scanning by @jpoehnelt in #649
- fix: auto-install binary on run if missing by @jpoehnelt in #654
- ci: add cargo-deny for license, advisory, and source auditing by @jpoehnelt in #653
- docs: update installation instructions to prioritize github releases by @jpoehnelt in #656
- refactor: drop serde_yaml by migrating to toml by @jpoehnelt in #657
- chore: release versions by @googleworkspace-bot in #655

What's Changed
- chore: remove cargo-dist, use native fetch for npm installer by @jpoehnelt in #646
- chore: release versions by @googleworkspace-bot in #647

- 674d53a: Fix Lint Skills CI job by installing uv via astral-sh/setup-uv before running uvx
- c7c42f6: fix: register script service and resolve test path validation errors
- 80bd150: feat(auth): use strict OS keychain integration on macOS and Windows
Closes #623. The CLI no longer writes a fallback .encryption_key text file on macOS and Windows when securely storing credentials. Instead, it strictly uses the native OS keychain (Keychain Access on macOS, Credential Manager on Windows). If an old .encryption_key file is found during a successful keychain login, it will be automatically deleted for security.
Linux deployments continue to use a seamless file-based fallback by default to ensure maximum compatibility with headless continuous integration (CI) runners, Docker containers, and SSH environments without desktop DBUS services.
- ec7f56b: Sync generated skills with latest Google Discovery API specs

Patch Changes
- 6a45832: Sync generated skills with latest Google Discovery API specs