v2.88.2: fix bogus VS Code version-mismatch warning

Bug fixes

• The VS Code extension's "binary in PATH is vX" version-mismatch warning no longer reports a bogus version. fallow-lsp (and fallow-mcp) did not handle --version: they started their stdio server, hit end-of-input, and exited with no output, so the extension's version probe got nothing back from the language server and its parser then accepted any number-shaped token from the surrounding output. An unrelated value (a Node banner such as Node.js v22.22.1, a digit in a sentinel path, or the npm launcher's appended verified: line) could surface as a warning like "binary in PATH is v22.22.1". The language server and MCP server now answer --version / -V / -v with their real version, and the extension only accepts a version in fallow's own <binary> <version> format (otherwise it treats the version as unknown rather than guessing). Thanks @melroy89 for the screenshot that surfaced it.

Full Changelog: v2.88.1...v2.88.2