[Ops]: Add Node version floor checks to openclawcode setup-check #83

Summary
Teach scripts/openclawcode-setup-check.sh to report whether the local Node version satisfies the refreshed-branch CLI startup floor.

Problem to solve
After the upstream refresh, the built CLI expects Node >=22.16.0, while this workstation still builds under 22.12.0 with warnings. Operators can currently pass most checks yet still fail when trying to start the refreshed-branch CLI directly.

Proposed solution
Update the setup-check path to surface the required Node floor explicitly.

• compare the local node --version against the generated CLI compatibility metadata when available
• emit a clear pass/warn/fail message that explains the current version and required floor
• keep the check visible in strict mode so operator promotion guidance does not assume the old floor

Add or adjust tests in src/openclawcode/testing/setup-check.test.ts to cover both a compatible and an out-of-date Node version.

Impact
Affected users/systems/channels
Operators promoting refreshed branches or trying to run the built CLI locally.

Severity
Medium.

Frequency
Whenever upstream raises the CLI startup floor or operators switch branches.

Consequence
Without an explicit setup check, operators can misread the environment as healthy even though the refreshed CLI will refuse to start.