Validate local ClickHouse versions during CLI parsing

[sdairs]

Summary

• parse local install, use, and server ClickHouse version operands into command-specific clap types
• reject malformed and unsupported version shapes with usage exit 2 before dispatch while preserving Postgres install selectors
• cover exact parsed variants, actionable errors, telemetry classification, whitespace-normalized selectors, and filesystem side effects

Design notes

• local remove <version> intentionally remains an opaque string because removal matches exact installed directory names rather than resolving version syntax
• UseVersionArg and ServerVersionArg intentionally remain separate so each command owns its accepted inputs and diagnostics

Tests

• cargo test -p clickhousectl
• cargo test -p clickhousectl local::cli::tests
• cargo test -p clickhousectl --test local_version_error_test
• cargo test -p clickhousectl --test telemetry_test invalid_local_versions_report_invalid_value_without_dispatch_side_effects
• cargo check -p clickhousectl --no-default-features
• cargo fmt --all --check
• cargo clippy -p clickhousectl --all-targets -- -D warnings

Closes #463

[sdairs]

Carry-over review from PR #485 (old PR for #463). This PR is a strict improvement over #485 (per-command types InstallVersionArg/UseVersionArg/ServerVersionArg satisfy acceptance criterion 4 "command-specific semantics explicit rather than assumed identical"; actionable postgres-selector errors; install help now documents postgres@18; no-side-effect assertions; no unrelated test edits). No sdairs review comments existed on #485. Three nits:

1. Stronger valid-forms assertions. Validate local ClickHouse version operands during CLI parsing #485's clap tests assert exact VersionSpec variants; this PR's valid-forms test only asserts version.to_string() == input round-trips, which is strictly weaker. Assert the parsed VersionSpec variant directly.

2. Document or validate local remove <version>. It remains an unvalidated String (both PRs). Defensible (remove matches installed dirs), but state that decision somewhere (code comment or PR description).

3. Consider collapsing UseVersionArg/ServerVersionArg. They are structurally identical and differ only in one error string. Either unify with a parameterized message or note why they are intentionally separate.

Cosmetic: leading-whitespace postgres@ input falls through to the generic numeric-parts error (prefix check precedes the parser's trim).