Call the `finishUp()` function upon `SIGINT`

[WesCossick]

If a SIGINT signal is received, we should call the finishUp() function to help ensure test projects are reset properly.

[WesCossick]

This is actually a little more difficult than expected. If you add...

process.on('SIGINT', async () => {
	console.log();
	await finishUp();
	process.exit();
});

...then it kind of works, but you encounter some quirks.

First, Yarn doesn't seem to exit when the running script exits. So even though Rugged is actually exiting, Yarn just hangs and you need to send another SIGINT to get it to exit:

You can see that this isn't the case whenever you run Rugged directly (not through yarn test):

The more problematic quirk is that Listr doesn't seem to cancel the currently running list, and there's no way to do so manually using its API. So sometimes the list can be printed twice, which isn't too bad:

But other times, it can look like this:

Notice that it not only flashed funny, but also continued on to the next Listr and started testing the test projects.

[pbelbin]

Notice that it not only flashed funny, but also continued on to the next Listr and started testing the test projects.

The 'flashing' reminds me of some of the computer graphics style used in 2001: A Space Odyssey.

Might be cool if it didn't repeat the information in some cases! :)