Review: a failure is the same by resource id, not by the host's words; bound files and /run/docker.sock are declared

The host's error text may carry a duration or a counter, and a resource looping on
it would never have read as stuck. The previous row is read and compared here.
Stuck needs a start to say. A container may mount the file a binding lands in; the
runtime socket is declared under both of its spellings; the catalogue-wide test
takes MESH_CATALOG.

internal/inventory/migrations/0025-a-failure-that-repeats-is-said-to-be-stuck.sql

@@ -7,8 +7,9 @@
 -- when its dependency arrives" from "failed identically for ever", and nothing escalated the second.
 --
 -- Still one row per node. What is added is how long the CURRENT failure has been the same one:
--- when it first appeared, and how many reports in a row have said it. A report that says something
--- different starts the count again; a clean apply clears it.
+-- when it first appeared, and how many reports in a row have said it -- the same outcome, the same
+-- refusal, the same failed resources by id (not by the host's words, which may carry a duration).
+-- A report that says something different starts the count again; a clean apply clears it.
 
 alter table node_report
     add column failing_since timestamptz,