Fuzztest config public -> private.

We hope to move to being able to build fuzztests into existing test
suites. At the moment, some of the compiler flags applied to fuzztest
are in a public_config and that could risk them applying to existing
unit test suites disabling useful warnings. We do not need this to be a
public config, so switch it back to private.

Bug: 40286211
Cq-Include-Trybots: luci.chromium.try:linux-libfuzzer-asan-rel,win-libfuzzer-asan-rel,linux-centipede-asan-rel
Change-Id: I4b513123ccc4424f84674048f54af70eb77516e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5465827
Commit-Queue: Paul Semel <paulsemel@chromium.org>
Reviewed-by: Paul Semel <paulsemel@chromium.org>
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Auto-Submit: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1289482}
NOKEYCHECK=True
GitOrigin-RevId: 94efc409e2ea326d3506c5ea0134f152e2cb26b1
1 file changed
tree: 491234a7287aefbe97b19279cbfe2cd605cabf91
  1. BUILD.gn
  2. OWNERS
  3. README.chromium