feat: add Java dynamic dedup sample

[officialasishkumar]

Pull Request Template

Description

Adds and commits the java-dedup sample app fixtures for Enterprise Java dynamic dedup replay validation.

The sample mirrors the Go dedup validation shape with 1000 committed Keploy tests split across four testsets of 250 tests each. CI should not run record mode for this path; it only replays these checked-in fixtures with keploy test --dedup to keep runtime predictable and save CI time.

Related issue: keploy/enterprise#1920
Related PRs: keploy/java-sdk#180, keploy/enterprise#1912, keploy/docs#839

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• mvn -B -DskipTests clean package in java-dedup.
• Verified committed fixture count: 1000 tests, four testsets, 250 tests per testset.
• Native replay with keploy test --dedup --pass-through-ports 36320: 1000 successes, 0 failures.
• Verified dedupData.yaml and duplicates.yaml are produced locally but ignored and not committed.

No unit tests were added by request; this sample is covered by replay and Enterprise pipeline validation.

Additional Context (Please include any Screenshots/gifs if relevant)

The Enterprise PR uses this branch from Woodpecker via SAMPLES_JAVA_REPO=https://github.com/officialasishkumar/samples-java.git and SAMPLES_JAVA_REF=codex/java-dedup-sample. The pipeline covers native, Docker, and restricted Docker modes across Java 8, 17, and 21 without recording.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings
• I have tagged the reviewers in a comment below incase my pull request is ready for a review
• I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

[officialasishkumar]

Upstream tracking issue: keploy/enterprise#1920