release: 0.0.7 — sparse bcachefs dev-N numbering

Bumps the package version to 0.0.7 to ship the fix for #11.

bcachefs assigns internal device indices at format / add time, so a
filesystem that's had devices added or removed can have arbitrary
gaps in `dev-N` numbering — a pool with five devices may expose
`dev-2` through `dev-6` with no `dev-0` or `dev-1`. The pre-0.0.7
discovery code probed sequentially from `dev-0` and `break`-ed on
the first missing one, so it bailed immediately on these layouts
and the mount-point string stayed empty. statvfs("") then errored,
the bcachefs CLI fallback also errored on the empty path, both
returned zero, and the top bar displayed `0.0/0.0 GiB`.

Now enumerates the actual `dev-*` entries via `read_dir` instead.
The reporter confirmed their layout (`dev-2 dev-3 dev-4 dev-5 dev-6`)
matches the predicted pattern, so this is the verified root cause.

Author: fenio

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "nasty-top"
-version = "0.0.6"
+version = "0.0.7"
 edition = "2024"
 license = "GPL-3.0-only"
 description = "A top-like TUI for bcachefs filesystems"