change the fuzzer timeout to 10s for normal CI builds

it is ridiculous to run multiple fuzzers for 5 minutes, even if
some of them run in parallel.  This means that even if the CI servers
are NOT overloaded, merges will be blocked for at least 5 minutes.

if the CI servers are overloaded, the fuzzers will block merges
for much longer.

Author: alandekok

.github/actions/fuzzer/action.yml

@@ -14,7 +14,7 @@ runs:
         # For fuzzing we won't be needing eapol_test
         mkdir -p build/tests/eapol_test
         : > build/tests/eapol_test/eapol_test.mk
-        make -j `nproc` test.fuzzer FUZZER_TIMEOUT=300
+        make -j `nproc` test.fuzzer FUZZER_TIMEOUT=10
         find build/fuzzer -type f ! -path 'build/fuzzer/*.log' | grep . && exit 1 || :
 
     - name: "Clang libFuzzer: Store assets on failure"