ci: tweak fuzzing config to report success when interrupted by timeout

[alex-ter]

For at least about a month, the fuzzing runs are actually mostly successful (bar some specific scripts: the one in #5140 and probably the one here: https://github.com/intel/cve-bin-tool/actions/runs/15817514178/job/44579076484), it's just that the runs were hitting the 1-hour timeout without causing any crashes, but the workflow was still considered failed due to exit code 130 reported in that case.

This tracking issue is to tweak the config/scripts to report such timeouts as workflow success, not failure. That way we will be able to clearly see the genuine fuzzing findings or infra problems.

I'll look into this when working on #5140, but if you want to take this, feel free (just post a note here).

[terriko]

This is a great idea, thank you!