Remove old tests and reexport libfuzzer from fuzzing module (#69)

* Remove unused regalloc2-test crate

This code doesn't build, and Chris says it's "a really old harness that
existed prior to building the fuzzing and was used mainly to profile and
get stats before integration with Cranelift".

* Re-export libfuzzer/arbitrary from fuzzing module

This avoids needing to keep dependencies on `arbitrary` in sync across
the three different Cargo.toml files in this project.

However, before version 0.4.2, libfuzzer-sys only supported using its
macros if it was available at the top-level `libfuzzer_sys` path, which
breaks when re-exporting it. So I'm upgrading to that version (or the
newest patch release of it).

Upgrading libfuzzer-sys in turn brings in the 1.0 release of the
arbitrary crate, with a minor API change along the way.

Cargo.toml

@@ -20,8 +20,7 @@ slice-group-by = "0.3.0"
 serde = { version = "1.0.136", features = ["derive"], optional = true }
 
 # The below are only needed for fuzzing.
-# Keep this in sync with libfuzzer_sys's crate version:
-arbitrary = { version = "^0.4.6", optional = true }
+libfuzzer-sys = { version = "0.4.2", optional = true }
 
 # When testing regalloc2 by itself, enable debug assertions and overflow checks
 [profile.release]
@@ -39,7 +38,7 @@ checker = []
 trace-log = []
 
 # Exposes the internal API for fuzzing.
-fuzzing = ["arbitrary", "checker", "trace-log"]
+fuzzing = ["libfuzzer-sys", "checker", "trace-log"]
 
 # Enables serde for exposed types.
 enable-serde = ["serde"]