fix: make --version exit with code 0 instead of 2

[mtorp]

Summary

• socket --version now exits with code 0 instead of code 2. The --version flag was parsed but never explicitly handled at the root command level, causing it to fall through to showHelp(2). This broke Ansible automation that checks exit codes.
• Fixed spurious "Received an unknown command: patch" error on every CLI invocation. The patch command was registered and public (hidden: false) but was commented out in the hardcoded command validation set.
• Added patch to the help output under "Local tools" so it's discoverable via socket --help.
• Bumped version to 1.1.75.

Test plan

• node dist/cli.js --version prints version string and exits with code 0
• No more "Received an unknown command: patch" in CLI output
• Added unit test verifying --version outputs semver and exits 0
• Existing --help and --dry-run tests pass with updated snapshots
• Verify on Linux that socket --version exits cleanly in Ansible context

---

Note

Low Risk
Low risk: changes are limited to root CLI flag handling and help/command listings, plus test/snapshot updates, with no impact on auth or data processing.

Overview
Ensures socket --version is explicitly handled at the root level by printing INLINED_SOCKET_CLI_VERSION and exiting with code 0 instead of falling through to help/error behavior.

Makes the patch subcommand a first-class public command by adding it to the validated root command set and the --help output, removing prior test output sanitization that hid “unknown command: patch”.

Adds a unit test covering --version output/exit code and bumps the package version to 1.1.75.

^{Written by Cursor Bugbot for commit a3a357d. Configure here.}