🐛 fix(fuzz): name the crashing target in CFLite output

[gaborbernat]

The ClusterFuzzLite summary that tools/fuzz/cflite.py prints named the sanitizer where it should name the fuzz target, and it listed each crash twice. On #1237's run (37787132229, undefined job) it reported a 46-byte input and a 3840-byte file as two crashes, both with "fuzzer": "undefined", so neither entry named the harness to reproduce.

CIFuzz saves each crashing input as out/artifacts/<target>/<sanitizer>/<input>, with the stack trace in <input>.summary beside it (_target_artifact_path and _save_crash). cflite.py took the file's parent directory, which is the sanitizer, and counted the .summary file as a second crash. It now names the first directory under out/artifacts and skips .summary files. The target name is not secret, and the summary still shows only a hash and size for each input.

[codspeed]

Merging this PR will degrade performance by 20.06%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 580 untouched benchmarks
⏩ 32 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	test_feature[shadow-slot-comments]	110.3 µs	138 µs	-20.06%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing gaborbernat:fix/cflite-crash-target (5f6c069) with main (d3c6243)}

Footnotes

1. 32 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩