I would like to be able to inspect the posix exit code in order to detect when Cypress cannot connect to the Cloud API, and a Cloud API request is necessary to continue. This primarily impacts record and parallel modes, where communication with Cypress Cloud is necessary to determine which spec should be executed next.

Acceptance Criteria:

• I can pass a --posix-exit-codes CLI flag, which changes Cypress' exit before to standard posix codes rather than the number of tests that fail
• When Cypress terminates due to a fatal cloud error and posix exit codes are in use, Cypress exits with code=112, which is not otherwise reserved.