Gemini CLI v0.50.0 fails to load .gemini/settings.json in VS Code Dev Container

### What happened?

The Gemini CLI does not load the workspace-level .gemini/settings.json configuration file when running inside a VS Code Dev Container.
This prevents any workspace-specific settings from being applied.

Steps to Reproduce:
1. In a dev container, confirm the workspace root with echo $GEMINI_CLI_IDE_WORKSPACE_PATH.
2. Create a file at /.gemini/settings.json.
3. Add the following content to the file:

1 {
2 "security.disableYoloMode": false
3 }
4. Ensure the file and directory have correct read permissions (drwxr-xr-x for the folder, -rw-r--r-- for the file).
5. Run gemini in the terminal.

Actual Behavior:
The CLI starts in normal mode and ignores the settings.json file completely, continuing to prompt for all actions. The settings file is not loaded.

### What did you expect to happen?

The CLI should start in YOLO mode, as dictated by the settings file.

### Client information

Client Information

Run `gemini` to enter the interactive CLI, then run the `/about` command.

```console
> /about
│ About Gemini CLI │
│ │
│ CLI Version 0.50.0 │
│ Git Commit 8d9733d53 │
│ Model Auto (Gemini 2.5) │
│ Sandbox no sandbox │
│ OS linux │
│ Auth Method Signed in with Google () │
│ Tier Gemini Code Assist Enterprise │
│ GCP Project │
│ IDE Client VS Code
```

### Login information

Logged in via google account

### Anything else we need to know?

* Gemini CLI Version: 0.50.0
* Gemini CLI Companion Extension Version: 0.20.0
* Host Environment: VS Code with Dev Containers extension

Start by reproducing the issue in a VS Code Dev Container using GEMINI_CLI_IDE_WORKSPACE_PATH, .gemini/settings.json, and the `gemini` terminal command. Trace the CLI's workspace settings loading path and verify that the configuration is applied in this environment, using `/about` and the expected YOLO-mode behavior as checks for completion.

Written by the indexing model from the issue text.