Renamed config -> cfg

Note this includes both the lfs3_config -> lfs3_cfg structs as well as
the LFS3_CONFIG -> LFS3_CFG include define:

- LFS3_CONFIG -> LFS3_CFG
- struct lfs3_config -> struct lfs3_cfg
- struct lfs3_file_config -> struct lfs3_file_cfg
- struct lfs3_*bd_config -> struct lfs3_*bd_cfg
- cfg -> cfg

We were already using cfg as the variable name everywhere. The fact that
these names were different was an inconsistency that should be fixed
since we're committing to an API break.

LFS3_CFG is already out-of-date from upstream, and there's plans for a
config rework, but I figured I'd go ahead and change it as well to lower
the chances it gets overlooked.

---

Note this does _not_ affect LFS3_TAG_CONFIG. Having the on-disk vs
driver-level config take slightly different names is not a bad thing.

runners/bench_runner.c

@@ -612,12 +612,12 @@ typedef struct bench_record {
     lfs3_emubd_io_t last_erased;
 } bench_record_t;
 
-static struct lfs3_config *bench_cfg = NULL;
+static struct lfs3_cfg *bench_cfg = NULL;
 static bench_record_t *bench_records;
 size_t bench_record_count;
 size_t bench_record_capacity;
 
-void bench_reset(struct lfs3_config *cfg) {
+void bench_reset(struct lfs3_cfg *cfg) {
     bench_cfg = cfg;
     bench_record_count = 0;
 }
@@ -1337,7 +1337,7 @@ void perm_run(
     // create block device and configuration
     lfs3_emubd_t bd;
 
-    struct lfs3_config cfg = {
+    struct lfs3_cfg cfg = {
         .context            = &bd,
         .read               = lfs3_emubd_read,
         .prog               = lfs3_emubd_prog,
@@ -1346,7 +1346,7 @@ void perm_run(
         BENCH_CFG
     };
 
-    struct lfs3_emubd_config bdcfg = {
+    struct lfs3_emubd_cfg bdcfg = {
         .disk_path          = bench_disk_path,
         .read_sleep         = bench_read_sleep,
         .prog_sleep         = bench_prog_sleep,