ci: fix fuzz jobs

[terriko]

It looks like our fuzzing jobs are failing during pip install due to a bazel error:

       <string>:28: DeprecationWarning: Use shutil.which instead of find_executable
      Extracting Bazel installation...
      Starting local Bazel server and connecting to it...
      Computing main repo mapping:
      WARNING: --enable_bzlmod is set, but no MODULE.bazel file was found at the workspace root. Bazel will create an empty MODULE.bazel file. Please consider migrating your external dependencies from WORKSPACE to MODULE.bazel. For more details, please refer to https://github.com/bazelbuild/bazel/issues/18958.
      Computing main repo mapping:
      Loading:
      Loading: 0 packages loaded
      WARNING: Couldn't auto load rules or symbols, because no dependency on module/repository 'rules_android' found. This will result in a failure if there's a reference to those rules or symbols.
      Loading: 0 packages loaded
      Loading: 0 packages loaded
      Loading: 0 packages loaded
      WARNING: Target pattern parsing failed.
      ERROR: Skipping '//:_mutator.so': error loading package '': Unable to find package for @@[unknown repo 'pybind11_bazel' requested from @@]//:build_defs.bzl: The repository '@@[unknown repo 'pybind11_bazel' requested from @@]' could not be resolved: No repository visible as '@pybind11_bazel' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
      ERROR: error loading package '': Unable to find package for @@[unknown repo 'pybind11_bazel' requested from @@]//:build_defs.bzl: The repository '@@[unknown repo 'pybind11_bazel' requested from @@]' could not be resolved: No repository visible as '@pybind11_bazel' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.

You can take a look at the various fuzz job logs here:
https://github.com/intel/cve-bin-tool/actions/workflows/fuzzing.yml

Not sure what's up, but it's probably a matter of following the instructions from Bazel. I'll mark this as potentially beginner-friendly.