💥(worker) Only respawn workers on crash (not failure)

[dubzzz]

Description

At the moment the worker package was not resilient to synchronous throws. As such doing so was considered identical to crashing the worker itself and caused new workers to be re-spawned.

With this PR, we properly handle synchronous throw triggered by the predicate. As such they are considered the same way as asynchronous ones.

Regarding isolation flags it changes a bit the behaviour. Following this change a synchronous throw will not trigger a new worker. New workers will only be created when the previous one crashes and exits.

Checklist — Don't delete this checklist and make sure you do the following before opening the PR

• The name of my PR follows gitmoji specification
• My PR references one of several related issues (if any)
  • New features or breaking changes must come with an associated Issue or Discussion
  • My PR does not add any new dependency without an associated Issue or Discussion
• My PR includes bumps details, please run yarn bump and flag the impacts properly
• My PR adds relevant tests and they would have failed without my PR (when applicable)

Advanced

• Category: 💥 Breaking change and 🐛 Fix a bug
• Impacts: Reboots of workers

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit b2170be:

Sandbox	Source
@fast-check/examples	Configuration

[github-actions]

👋 A preview of the new documentation is available at: http://6646513f64a029007d29f704--dubzzz-fast-check.netlify.app