refactor: explicitly import node:process

[Fdawgs]

This PR improves static analysis by explicitly importing node:process rather than relying on the global process. Helps provide better type inference for TypeScript and autocomplete and error detection for IntelliSense in VS Code.

Checklist

• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[Copilot]

Pull request overview

This PR refactors the codebase to explicitly import from node:process instead of relying on the global process object, improving static analysis, type inference, and IDE autocomplete support.

• Explicitly imports specific node:process exports (env, stdin, stdout, exit)
• Replaces all global process usages with the imported named exports
• Affects authentication, I/O operations, and process control logic

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
github-api.js	Imports env and uses it for GitHub token authentication
commands/utils/remove-from-npm.js	Imports env for npm spawn environment configuration
commands/utils/input.js	Imports stdin and stdout for readline interface
commands/onboard.js	Imports exit for process termination
commands/offboard.js	Imports exit for process termination

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The spawn call now passes only the imported env object (which contains environment variables like GITHUB_TOKEN) instead of the full process.env. This changes the behavior - spawn expects the env option to be a complete environment object with all necessary variables (like PATH, HOME, etc.), not just a subset. The spawned npm process will lack critical system environment variables and will likely fail. Change to { env: env } to maintain the original behavior, or import the entire process.env if the intent was to pass all environment variables.