cargo-nextest 0.9.86-b.4

Since beta 3:

Added

• Setup scripts are now represented in the JUnit output. For more information,
  see Setup scripts in JUnit output.

Changed

• Each test now has a separate Tokio task associated with it. This leads to
  greater reliability (each test's task can now panic independently), and is
  faster in repos with many small tests.

  For example, in one test done against
  clap-rs/clap on Linux, cargo nextest run goes down from 0.36 seconds to 0.23 seconds.

Fixed

• Fixed a bug where pressing two Ctrl-Cs in succession would not SIGKILL any running tests.
• junit.store-success-output now works correctly -- previously, storage of output is disabled unconditionally.
• In JUnit output, the testsuite elements are now stored in the order they are first seen (IndexMap), rather than in random order (HashMap).