Extend `cargo run -- continuous` optionally to output HTML with stats

[frewsxcv]

It'd be very cool if there was a flag that would output HTML after each fuzzing attempt with stats about all the projects that have been fuzzed by cargo run -- continuous. Then it would be possible to spin up a VPS, setup nginx, run cargo run -- continuous in the background, and monitor fuzzing from a web browser ✨

I got excited by this idea and bought http://fuzz.rs 😄

[frewsxcv]

The main challenge here is figuring out how to gather statistics from the fuzzers.

Ideally, for each fuzz target, we'd output in HTML:

• <fuzz target name>
  • <coverage information>
  • <number of crashes found>
    • <links to download the crashes>
  • <link to fuzz target on github>

[frewsxcv]

For reference, cargo run -- continuous isn't in master yet, it's in this pull request though

[PaulGrandperrin]

That's funny, I'm already doing a poor's man version of that with tmux and gotty on my local network.

IMO, we should also get in contact with https://github.com/google/oss-fuzz to get some feedback from their experience of managing a fuzzing cluster.