stop showing Fuzz action failure on success

[a10y]

Annoyingly, our Fuzz CI action always shows as failing even when it's succeeding:

We're checking for the wrong thing to determine if there were crashes. The artifacts dir is always created when you run the fuzzer.

We should be checking if there are any crash files in there.

[codspeed-hq]

Merging this PR will degrade performance by 11%

⚡ 7 improved benchmarks
❌ 1 regressed benchmark
✅ 972 untouched benchmarks
🆕 20 new benchmarks
⏩ 1466 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	take_map[(0.1, 1.0)]	4.2 ms	3.5 ms	+18.64%
⚡	Simulation	take_map[(0.1, 0.5)]	2.6 ms	2.1 ms	+24.35%
⚡	Simulation	take_map[(0.1, 0.1)]	1,007.5 µs	907.4 µs	+11.04%
🆕	Simulation	sequence_decompress_u32	N/A	4.1 ms	N/A
🆕	Simulation	sequence_compress_u32	N/A	5.2 ms	N/A
⚡	Simulation	take_200k_first_chunk_only	4.2 ms	3.3 ms	+26.45%
⚡	Simulation	patched_take_200k_first_chunk_only	5.4 ms	4.8 ms	+11.98%
⚡	Simulation	patched_take_200k_dispersed	5.6 ms	4.7 ms	+19.84%
⚡	Simulation	take_200k_dispersed	4.5 ms	3.6 ms	+24.37%
🆕	Simulation	decompress_utf8[(10000, 1024)]	N/A	112.5 µs	N/A
🆕	Simulation	decompress_utf8[(1000, 16)]	N/A	30.9 µs	N/A
🆕	Simulation	decompress_utf8[(1000, 4)]	N/A	42.6 µs	N/A
🆕	Simulation	decompress_utf8[(10000, 16)]	N/A	136 µs	N/A
🆕	Simulation	decompress_utf8[(1000, 256)]	N/A	28.6 µs	N/A
🆕	Simulation	decompress_utf8[(10000, 256)]	N/A	113.2 µs	N/A
🆕	Simulation	decompress_utf8[(100000, 1024)]	N/A	946.8 µs	N/A
🆕	Simulation	decompress_utf8[(100000, 16)]	N/A	1.2 ms	N/A
🆕	Simulation	decompress_utf8[(10000, 4)]	N/A	209.8 µs	N/A
🆕	Simulation	decompress_utf8[(100000, 4096)]	N/A	944.7 µs	N/A
🆕	Simulation	decompress_utf8[(100000, 256)]	N/A	958.2 µs	N/A
...	...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

---

_{Comparing ci-fuzz-fix (a87c7e3) with develop (5d6a3c8)²}

Footnotes

1. 1466 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. ↩

2. No successful run was found on develop (4cbfb33) during the generation of this report, so 5d6a3c8 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩