fix: the Open/Resolved and Chains filters apply an exact rule's slash, case and query options (WR-22)

coveredSQL and chainSQL compared the source literally, so /missing/ or
/missing?utm=x stayed open after /missing answered it, and /a -> /b/ was
no chain next to /b. Both now use one SQL form of the runtime's exact
match (prefiltered on the indexed source_key). Pattern and regex rules
remain with the per-row badge, which the list_not_found schema text now
says.

controllers/api/notfound.go

@@ -71,7 +71,7 @@ type ListNotFoundInput struct {
 	Page    int    `json:"page,omitempty" query:"page" jsonschema:"the page number, from 1"`
 	PerPage int    `json:"per_page,omitempty" query:"per_page" jsonschema:"rows per page, at most 200 (50 by default)"`
 	Search  string `json:"search,omitempty" query:"search" jsonschema:"text the address contains"`
-	Status  string `json:"status,omitempty" query:"status" jsonschema:"open (no redirect answers the address yet) or resolved"`
+	Status  string `json:"status,omitempty" query:"status" jsonschema:"open or resolved: whether an exact redirect or 410 answers the address, with its case, trailing-slash and query options; an address only a pattern or regex rule answers stays open here but has resolved true in its row"`
 }
 
 // NotFoundIDInput names one 404 log entry.