v7.6.0+ supresses Webpack errors on `electron-forge start` when not using DEBUG flag

### Pre-flight checklist

- [x] I have read the [contribution documentation](https://github.com/electron/forge/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project uses.
- [x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

### Forge version

7.7.0

### Electron version

34.3.0

### Operating system

macOS 15.3.1

### Last known working Forge version

7.5.0

### Expected behavior

`electron-forge start` displays any Webpack errors that prevent the command from succeeding.

### Actual behavior

`electron-forge start` silently exits with non-zero exit code.

### Steps to reproduce

1. Create a new Forge app with e.g. `npx create-electron-app@latest test-app --template=webpack-typescript`
2. Easiest test for me was to reserve port 9000 (logger) for something. E.g. `mkdir -p ~/tmp-http && npx http-server -p 9000 ~/tmp-http`. Or you can set `loggerPort` in forge.config.ts WebpackPlugin to a known in-use port.
3. Try to run `electron-forge start` or `npm start`.

### Additional information

When using `DEBUG=electron-forge:*`, then the errors do show up but seems like an unnecessary hassle for development. Especially when migrating from v7.5.0