Handle Xvfb exiting immediately on spawn with 1 exit code

I noticed today there is an edge case we specifically do not handle.

If Xvfb spawns and then immediately exits due to argument or permission errors, it will close with `1` exit code. Due to the way we call into this, the CLI will just "hang" forever.

This could be why some linux users have detected Cypress "hanging" initially on run without any output.

We need to update `@cypress/xvfb`.