Fixes MCP installation issues when using remote environments like WSL, SSH, or containers.

Summary

• Adds environment-scoped global storage to prevent data conflicts
• Adds remote instance identifier to differentiate between remote setups
• Moves environment-specific data to scoped storage

Impact

Users can now reliably install and use the GitKraken MCP across different remote environments without conflicts.

Validation

1. Connect to a WSL or SSH remote environment
2. Install the GitKraken MCP
3. Verify installation succeeds and persists correctly
4. Switch to a different remote environment and repeat

Risk

Low - storage migration is backwards compatible.