Scoop Godot Installation running in the background (terminal/console/command line)

### Tested versions

- Reproducible in 4.2.stable.

### System information

Windows 10

### Issue description

I am using godot-rust, and I need the standard output and error for debugging purposes of my code, so I followed the command line installation documentation and installed godot through scoop. The problem is, every time I run the command, nothing gets printed, and I am able to execute other commands. I talked about it in the godot-rust server and it seems likely that the scoop intallation might be running godot on the background, but it should be in the foreground, since I believe it is more useful to be able to see the output than, just not.

### Steps to reproduce

Install Scoop:
```
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression
```

Add bucket extras:
```
scoop bucket add extras
```

Install godot:
```
scoop install godot
```

Run godot:
```
godot
```

### Minimal reproduction project (MRP)

No project is necessary.

Reproduce the issue on Windows 10 using the listed Scoop installation steps, then run the `godot` command and observe whether its standard output and error remain attached to the terminal. Done means a Scoop-installed Godot process runs in the foreground and exposes its output for debugging.

Written by the indexing model from the issue text.