#17912: fix: configure git to use HTTPS instead of SSH for GitHub URLs

## Summary When running `openclaw update` on a non-git install (global npm install), packages with git dependencies (like `whiskeysockets/libsignal-node`) were failing with "Permission denied (publickey)" error because npm tried to access them via SSH. This fix configures git to use HTTPS instead of SSH for GitHub URLs during the global update step by setting the `GIT_CONFIG_PARAMETERS` environment variable. ## Changes - Modified `src/infra/update-runner.ts` to pass git HTTPS configuration via environment variable when running global npm/pnpm/bun install ## Testing - All existing tests in `src/infra/update-runner.test.ts` pass (13 tests) - TypeScript compilation passes - Code formatting verified Fixes openclaw/openclaw#17907 <!-- greptile_comment --> <h3>Greptile Summary</h3> Fixes SSH authentication errors when installing packages with git dependencies during global `openclaw update` by configuring git to use HTTPS instead of SSH for GitHub URLs via the `GIT_CONFIG_PARAMETERS` environment variable. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The change is minimal, well-scoped, and addresses a specific SSH authentication issue. It only adds environment configuration for the global update step without modifying any other logic. All existing tests pass, and the solution follows standard git configuration practices. - No files require special attention _{Last reviewed commit: 863e350} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->