I was alerted via b/323340435 that the current primary contact is a
public Google Group. Changing the contact to myself to prevent early
disclosure of detected vulnerabilities.
1. Add `centipede` to `DEFAULT_ENGINES`.
2. Remove the `fuzzing_engines` attribute from `project.yaml`s if
redundant (i.e., all default engines are included in that YAML file).
3. Temporarily disable `centipede` on `c`/`c++` projects that previously
use all `DEFAULT_ENGINES` (200 projects did not specify
`fuzzing_engines` in `project.yaml`) so that we can gradually enable
centipede later them later.
Continuing #8690.
Given that `Centipede` passed CI tests of the 5 projects in #8690, we
will gradually roll it out to let more real-world fuzzing targets
benefit from it.
The second round contains the following 5 projects, **some of which are
not from Google** (unlike round 1):
1. `skcms`,
2. `abseil-cpp`,
3. `alembic`,
4. `arduinojson`,
5. `aspell`.
Projects are selected because:
1. They are `C++` projects.
There will be another round (of 10 projects) as soon as we can confirm
that Centipede works fine in this round.