Added cluster fuzz lite

[FlawzyByte]

I've added a small Jazzer harness under fuzz/ plus a ClusterFuzzLite layout in .clusterfuzzlite/ (Dockerfile, build.sh, and a minimal project.yaml).
The harness exercises parsing and utility paths that see untrusted data (JSON, dates, strings) without touching pom.xml, so normal Maven builds stay as they are; the Docker script pins apis-bom the same way CI does, builds the jar, pulls runtime deps, and compiles the fuzzer the way OSS-Fuzz-style JVM projects usually do. The goal is better supply-chain hygiene for OpenSSF Scorecard’s fuzzing signal and a clear path to wire this into OSS-Fuzz or PR fuzzing later, without dragging Jazzer into every developer’s default classpath and every other repo.
Note: 2nd PR for removing extra licensing.

[subhramit]

Use the full name jsonObject (or anything more relevant/descriptive) here.
As Java people, we commit to having descriptive variable names :)

[FlawzyByte]

You have a solid point here, as "jo" might be misleading.
I'll change it to simply jsonobject 👍🏼

[axmsoftware]

Interesting feature. Would you like to demo it?

[FlawzyByte]

Yes Miss arila, as it mentioned in the scorecard that Fuzzing is needed,
So basically fuzzing is a way to find bugs by inputting to the program/app lots of strange or random inputs to see what breaks.
Think of it like throwing weird combinations of letters, numbers, or files (often auto, multiple times) and watching for crashes, errors, or odd behavior.
When the program misbehaves, that gives us a clue where the code is fragile or insecure so we can patch it faster.
Compared to heavier platforms(OSSFuzz, ClusterFuzz, AFL++), ClusterFuzzLite is simpler to set up and CI-friendly on modest hardware.

[subhramit]

One more request - please camelCase