There doesn't seem to be a way for projects with `view_restrictions: none` to make all the OSS-Fuzz issues public

It would be great if it was possible to make https://oss-fuzz.com/testcases?project=libbpf public. It should help to point duplicates like https://github.com/libbpf/libbpf/issues/634, https://github.com/libbpf/libbpf/issues/682, https://github.com/libbpf/libbpf/issues/683 and https://github.com/libbpf/libbpf/issues/688 to that dashboard. All those issues have already been found by the libbpf fuzz target on OSS-Fuzz (and I suspect most of those issues were "discovered" by just building and running it as well) but, for example, https://oss-fuzz.com/testcase-detail/4792745105686528 hasn't been officially reported because it was delayed.

I don't think it can prevent anyone from spamming the libbpf issue tracker with those duplicates but at least it should help to close them with a link to the list of known issues.

The request centers on the OSS-Fuzz dashboard at oss-fuzz.com/testcases?project=libbpf and the project setting view_restrictions: none. Start by tracing how that setting controls testcase visibility; done means a project configured with none can expose all its testcases publicly, including known cases that have not been officially reported.

Written by the indexing model from the issue text.