Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

All committers have signed the CLA.

@tgriesser is this another example of something that we could catch higher up in the data-context in GUI mode?

@flotwig This is another example of an unhandledRejection which we are currently treating as a fatal error in all cases. I think the adjustment would be to send error reports on these / log to the console but not crash open mode on them.

@tgriesser we should exit on unhandledRejections always since it means the program is in an undefined state. I'm not super familiar with this area, do you know off the top of your head how this is being called? If it's in response to a GraphQL query, etc.

It's because we're not await'ing the promise:

try {
  return nmi.machineId()
} catch (error) {
  return undefined
}

vs

try {
  return await nmi.machineId()
} catch (error) {
  return undefined
}

the former will lead to an unhandledRejection if it throws and isn't caught higher up in the chain - which it isn't because it's not in the try block in getLatestVersion, same problem as #22099.

Has nothing to do with GraphQL, it's more to do with the fact that we're now using async/await rather than promise chains everywhere and not always ensuring there's proper awaiting. I think it's something we can introduce linting for but IIRC there were problems with false positives & negatives.