Extend the fuzzer to check the debug locations output

The checker only checks for the correctness of the allocation dataflow but not for the debug locations output. Although the correctness of the debug locations output isn’t so critical, I think having it checked will still be a good idea, even if it’s just for testing.

Inspect the existing fuzzer checker and its allocation dataflow validation, then trace how debug locations output is produced. Extend the checker so it also validates debug locations, and confirm that the fuzzer checks both allocation dataflow and debug locations.

Written by the indexing model from the issue text.