Exit `next dev` with a non-zero code when next.config.js is invalid (#83602)
In `next dev`, we're currently ignoring the exit code of the spawned
child process, and always exiting with `0` instead. We should exit the
process with the child's exit code instead. This is relevant when the
`next.config.js` is invalid, for example.