Revamp Log4j tests

[vy]

I am an Apache Logging Services (the Apache Software Foundation project responsible for Log4j, Log4cxx, Log4net, etc. subprojects) PMC member – see the team. This PR revamps the Log4j tests with following changes:

• Replaced existing tests¹ with new, improved ones in the fuzzing branch² of the official Log4j repository. This will not only ensure that tests will be maintained as a part of the official project, also enables maintainers to introduce new tests, make changes, etc. without touching the OSS-Fuzz code base.

• Introduced JSON dictionary and seed corpus for fuzzing JSON-related Log4j components

• Rewrote Dockerfile to match the JDK version to the one used by the official Log4j project.

• Delegated build.sh to the one provided in the official Log4j distribution. This enables maintainers to introduce new tests, make changes, etc. without touching the OSS-Fuzz code base.

• Rewrote project.yaml such that

  • Interested PMC members were added as primary_contact
  • Removed existing vendor_ccs, since found vulnerabilities should not be disclosed to individuals outside the PMC

• Renamed log4j2 project folder to apache-logging-log4j2 to comply with the naming convention followed by other ASF projects integrated with OSS-Fuzz

¹ Existing tests were not even compiling anymore due to bit rot.
² I choose using a dedicated branch to carry out the development. Once I have a ClusterFuzz account and see things moving, I will merge the fuzzing branch to 2.x, the branch serving Log4j 2 releases.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

vy is a new contributor to projects/log4j2. The PR must be approved by known contributors before it can be merged. The past contributors are: fmeum, henryrneh, aschaich, 0roman
vy is integrating a new project:
- Main repo: https://github.com/apache/logging-log4j2
- Criticality score: N/A

[fmeum]

LGTM

I also looked at the fuzz tests on the fuzzing branch in the log4j repo and they look much, much better than the basic tests I added as part of the initial integration. Great work! You may want to apply for an integration reward.

[vy]

Hey @DavidKorczynski! Thanks for triggering the CI. There, out of 11, only the build (libfuzzer, address, x86_64) check has failed, but the error message doesn't make much sense to me. Do you mind helping out, please?

[fmeum]

@DavidKorczynski Could you review for approval?

[DavidKorczynski]

Thanks @vy and @fmeum !!

[DavidKorczynski]

Renamed log4j2 project folder to apache-logging-log4j2 to comply with the naming convention followed by other ASF projects integrated with OSS-Fuzz

Could we avoid doing this please, and keep it in the same folder? Due to the backend running OSS-Fuzz we prefer to not change the name