hermes - 💡(How to fix) Fix Profile HOME isolation can hide existing GitHub CLI auth from subprocesses [2 pull requests]

Bug

When Hermes profile HOME isolation is active, subprocesses can lose access to an existing host-level GitHub CLI auth config.

That makes commands such as gh auth status, git push, or gh pr create appear unauthenticated inside a profiled Hermes subprocess even when the OS account is already authenticated.

Reproduction

1. Authenticate GitHub CLI on the OS account.
2. Run a Hermes profile that rewrites HOME for subprocess isolation.
3. Run gh auth status or a GitHub operation inside that profiled subprocess.
4. gh does not see the existing account-level config if the profiled HOME has no gh config.

Expected

Profile isolation should remain intact, but foreground/background terminal subprocesses should preserve usable GitHub CLI auth when the OS account already has it.

Proposed fix

If a profiled subprocess HOME has no gh config but the OS account does, set GH_CONFIG_DIR to the account-level gh config directory for both foreground and background terminal environments.

Relevant files from the closed PR draft:

• tools/environments/local.py
• tests/test_subprocess_home_isolation.py

Related: #29015 covers a similar profile-HOME isolation class of issue for macOS CLI auth.

Originally proposed as PR #29503, now converted to an issue to avoid maintaining a contributor fork.