fix: Avoid running linters on files in fuzz/generated

[terriko]

Description

Reldated:

• feat: fuzz testing for GoModParser #3434

It came up in #3434 that our CI system is running linters on files in fuzz/generated -- since these are generated files and not intended for us to edit, we should probably ignore those. I'm guessing we'll need to add something to the config for black, isort and other tools, and we may need to modify the CI job to make sure that it uses config if there isn't a file already in use, and make sure that the same stuff is used when pre-commit is run locally.

The pre-commit config can be found here:
https://github.com/intel/cve-bin-tool/blob/main/.pre-commit-config.yaml

You can see in there that black has its own config file here:
https://github.com/intel/cve-bin-tool/blob/main/bandit.conf

To reproduce

Steps to reproduce the behaviour:

1. Add in a file in fuzz/generated to a PR
2. Run tests in github ac tions

Expected behaviour:

• File in the generated/ directory should be ignored

Actual behaviour:

• isort, black, flake8 seem to run on files in the fuzz/generated directory and may report errors.

[mastersans]

Hey can i work on this issue?