fix(search, searchset): --quick reports no row when nothing matched

[jqnatividad]

On an unindexed file, --quick printed the total row count to stderr when nothing matched. That's the same place a match's row number goes, so callers can't tell a no-match from a match on the last row.

• search --quick printed it on every no-match, then exited 1.
• searchset --quick --not-one printed it and exited 0. That is exactly what a caller sees for a real match. DataPusher+'s quick PII screen ran into this: fix(pii): make PII screening work with its default regexes datapusher-plus#343 had to avoid --not-one and read the exit code instead.

The indexed (parallel) path already printed nothing on no-match. The sequential path now matches it and prints the row only when there was a match.

--quick on unindexed input, no match	before	after
search	row count on stderr, exit 1	nothing, exit 1
search --not-one	row count on stderr, exit 0	nothing, exit 0
searchset	nothing, exit 1	nothing, exit 1
searchset --not-one	row count on stderr, exit 0	nothing, exit 0

Tests: search_quick_nomatch_reports_no_row and searchset_quick_nomatch_reports_no_row cover plain --quick, --quick --not-one, and the indexed --jobs 2 path. I mutation-checked them: with the fix reverted, both fail, with stderr "4\n" and "6\n" (the row counts). The search and searchset suites pass on all_features, lite and datapusher_plus. clippy and double-run-check are clean.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}