Ability to restart `DuskServer` process between tests

[crynobone]

̄At the moment, DuskServer will run the same process for each Test class via setUpBeforeClass and tearDownAfterClass, and I would experience failure when a test class contains large enough test methods.

1) Laravel\Nova\Tests\Browser\IndexTest::resource_index_can_show_contents_even_when_set_as_collapsed
Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session/5d333faa132af32572a5848301ddd612/frame with params: {"id":null}

Operation timed out after 30005 milliseconds with 0 bytes received

/Users/crynobone/Projects/laravel/nova/aries/vendor/php-webdriver/webdriver/lib/Remote/HttpCommandExecutor.php:333
/Users/crynobone/Projects/laravel/nova/aries/vendor/php-webdriver/webdriver/lib/Remote/RemoteWebDriver.php:585
/Users/crynobone/Projects/laravel/nova/aries/vendor/php-webdriver/webdriver/lib/Remote/RemoteExecuteMethod.php:27
/Users/crynobone/Projects/laravel/nova/aries/vendor/php-webdriver/webdriver/lib/Remote/RemoteTargetLocator.php:35
/Users/crynobone/Projects/laravel/nova/aries/vendor/laravel/dusk/src/Browser.php:295
/Users/crynobone/Projects/laravel/nova/aries/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:144
/Users/crynobone/Projects/laravel/nova/aries/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php:261
/Users/crynobone/Projects/laravel/nova/aries/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:150
/Users/crynobone/Projects/laravel/nova/aries/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:71
/Users/crynobone/Projects/laravel/nova/aries/tests/Browser/IndexTest.php:432

This can be solved by splitting the tests into 2 or 3 different Test classes but I would like if we can explore the ability to restart the DuskServer in between tests.