Run the fuzzers in the CI

[sylvestre]

just like the coreutils, we should run the fuzzers in the CI to make sure we don't regress

https://github.com/uutils/coreutils/blob/main/.github/workflows/fuzzing.yml as example

[hanbings]

hello!
I submitted a fuzzing.yml ci file and made minor modifications to the original code in #29, but I forgot to pick up the issues here in advance, I hope it doesn't disrupt your work.

Here are some other issues I've encountered:

1. Noticed that both the Windows build and macOS before I forked didn't work.
2. Although the CI is passing, it doesn't seem to be testing properly.
   here is the fuzzing ci log built on my fork: https://github.com/hanbings/diffutils/actions/runs/8331273334/job/22797824794
   in the Run fuzz_ed for XX secords step, cargo threw an error in the console, but did not interrupt the CI.

Do I need to create some ci action to get full logs from ci? or where should I start to check the fuzzed code?

[hanbings]

Excuse me, I noticed that a recent commit changed the parameters of the diff function, and I have now modified the code of the fuzz test so that it builds properly. PR: #32

[sylvestre]

done here: https://github.com/uutils/diffutils/actions/workflows/fuzzing.yml