feat: attach Java dedup agent in sample

[officialasishkumar]

Pull Request Template

Description

Updates the Java dynamic dedup samples so applications do not compile against the Keploy SDK. The SDK is copied as a runtime Java agent and attached with -javaagent.

Key changes:

• Uses io.keploy:keploy-sdk:2.0.2 for the copied runtime Java agent.
• Adds Spring Boot Java dedup sample wiring for runtime keploy-sdk.jar agent attachment.
• Adds Dropwizard/Jersey dedup sample coverage for non-Spring Java apps.
• Covers jar, classpath, Docker, distroless, restricted Docker, and restricted classpath launch styles.
• Adds checked-in Keploy fixtures so Enterprise CI can replay instead of recording during CI.
• Uses stable sample jar names: target/java-dedup.jar and target/dropwizard-dedup.jar.
• Adds Dropwizard Docker fixes so runtime artifacts are included in the Docker build context and distroless runs with the same runtime user contract as the Spring sample.

Fixes # NA

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?

• git diff --check -- java-dedup/README.md dropwizard-dedup/README.md
• Verified the sample READMEs reference keploy.agent.version=2.0.2
• Earlier branch validation covered Spring Boot and Dropwizard builds, Java agent manifest checks, no Keploy imports in sample application code, Docker Maven builds for Java 8 and 21, host smoke on Java 17, and workflow YAML parsing.

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

Related PRs:

• Java SDK agent: feat: run Java dedup as java agent java-sdk#183
• Enterprise CI: https://github.com/keploy/enterprise/pull/1959
• Docs: docs: document Java dedup agent setup docs#848

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 smoke and workflow coverage that proves the feature works
• 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) by adding "--signoff" to my git commit command.

[khareyash05]

LGTM