Reworked bench.py/bench_runner/how bench measurements are recorded

This is based on how bench.py/bench_runners have actually been used in
practice. The main changes have been to make the output of bench.py more
readibly consumable by plot.py/plotmpl.py without needing a bunch of
hacky intermediary scripts.

Now instead of a single per-bench BENCH_START/BENCH_STOP, benches can
have multiple named BENCH_START/BENCH_STOP invocations to measure
multiple things in one run:

  BENCH_START("fetch", i, STEP);
  lfsr_rbyd_fetch(&lfs, &rbyd_, rbyd.block, CFG->block_size) => 0;
  BENCH_STOP("fetch");

Benches can also now report explicit results, for non-io measurements:

  BENCH_RESULT("usage", i, STEP, rbyd.eoff);

The extra iter/size parameters to BENCH_START/BENCH_RESULT also allow
some extra information to be calculated post-bench. This infomation gets
tagged with an extra bench_agg field to help organize results in
plot.py/plotmpl.py:

  - bench_meas=<meas>+amor, bench_agg=raw - amortized results
  - bench_meas=<meas>+div,  bench_agg=raw - per-byte results
  - bench_meas=<meas>+avg,  bench_agg=avg - average over BENCH_SEED
  - bench_meas=<meas>+min,  bench_agg=min - minimum over BENCH_SEED
  - bench_meas=<meas>+max,  bench_agg=max - maximum over BENCH_SEED

---

Also removed all bench.tomls for now. This may seem counterproductive in
a commit to improve benchmarking, but I'm not sure there's actual value
to keeping bench cases committed in tree.

These were alway quick to fall out of date (at the time of this commit
most of the low-level bench.tomls, rbyd, btree, etc, no longer
compiled), and most benchmarks were one-off collections of scripts/data
with results too large/cumbersome to commit and keep updated in tree.

I think the better way to approach benchmarking is a seperate repo
(multiple repos?) with all related scripts/state/code and results
committed into a hopefully reproducible snapshot. Keeping the
bench.tomls in that repo makes more sense in this model.

There may be some value to having benchmarks in CI in the future, but
for that to make sense they would need to actually fail on performance
regression. How to do that isn't so clear. Anyways we can always address
this in the future rather than now.

runners/bench_runner.h

@@ -19,12 +19,26 @@ void bench_trace(const char *fmt, ...);
 #define LFS_TRACE(...) LFS_TRACE_(__VA_ARGS__, "")
 #define LFS_EMUBD_TRACE(...) LFS_TRACE_(__VA_ARGS__, "")
 
-// provide BENCH_START/BENCH_STOP macros
-void bench_start(void);
-void bench_stop(void);
+// BENCH_START/BENCH_STOP macros measure readed/proged/erased bytes
+// through emubd
+void bench_start(const char *meas, uintmax_t iter, uintmax_t size);
+void bench_stop(const char *meas);
 
-#define BENCH_START() bench_start()
-#define BENCH_STOP() bench_stop()
+#define BENCH_START(meas, iter, size) \
+    bench_start(meas, iter, size)
+#define BENCH_STOP(meas) \
+    bench_stop(meas)
+
+// BENCH_RESULT/BENCH_FRESULT allow for explicit non-io measurements
+void bench_result(const char *meas, uintmax_t iter, uintmax_t size,
+        uintmax_t result);
+void bench_fresult(const char *meas, uintmax_t iter, uintmax_t size,
+        double result);
+
+#define BENCH_RESULT(meas, iter, size, result) \
+    bench_result(meas, iter, size, result)
+#define BENCH_FRESULT(meas, iter, size, result) \
+    bench_fresult(meas, iter, size, result)
 
 
 // note these are indirectly included in any generated files