scan-next: log real dedupes the do-nothing floor declines
plan_accept_null counts every extent where the do-nothing floor wins, but
that lumps together the common no-duplicates case with the diagnostically
interesting one: an extent where a real covering was built and then lost
to the floor because its reference/extent cost outweighed the space it
would free. Only the counter moved; nothing said which extents, how much
they would have freed, or why the floor rejected them.
Emit a "plan: null" log line when the floor wins and the best competing
real plan has a non-zero operation count. The zero-op case (no duplicate
found, or none surviving the gates) ties the floor at debt 0 and stays
silent, so the line does not fire for every scanned extent. When it does
fire the losing plan's debt is necessarily >= 0 (a negative-debt plan
would have displaced the floor), so the line reports the aggregate cost
that sank it: bytes_freed found, physical_freed earned, refs_added /
refs_created spent, extents_delta, and the positive space debt. This is
the ref-cost-vs-physical-freed breakdown that names the cause -- a
compressed dst freed wholesale earns little physical credit against the
references its removal must rewrite.
Add plan_null_declined alongside so the interesting subset of
plan_accept_null is countable without grepping.