[llvm] [DevPolicy] Add guidelines for fuzzer-generated issue reports (PR #112372)

[Shafik Yaghmour via llvm-commits]

https://github.com/shafik commented:

A few things to consider based on my recent effort screening recent fuzzing work against the clang frontend.

In general I ask them to provide godbolt links.

Properly format code using ` ```cpp ` and properly format backtraces using ` ```console `

For crashes, I am asking folks to:

- check how far back the crash goes. If they can label they should label appropriately e.g. `regression:19` for clang-19 regressions. Recent work has caught several clang-19 regressions which is really valuable.

- Should make an effort to look for duplicate and or related bugs and link them in the bug report.

These really ease my effort in screening these bugs and allow me to more quickly prioritize them.   

https://github.com/llvm/llvm-project/pull/112372