docs: document Java dedup agent setup

[officialasishkumar]

What has changed?

Documents the Java dynamic dedup runtime-agent flow using io.keploy:keploy-sdk:2.0.2. The docs now say the Keploy SDK should be copied as a Java agent, not added as an application dependency, and application code should not import Keploy classes.

The Java guide covers:

• attaching the Keploy Java agent and JaCoCo agent with -javaagent
• in-process JaCoCo runtime coverage and TCP fallback
• Maven/Gradle classes, Spring Boot jars, Dropwizard/Jersey apps, classpath apps, servlet/WAR layouts, and custom KEPLOY_JAVA_CLASS_DIRS
• Docker and restricted Docker socket requirements
• running keploy test --dedup --language java
• Apache Karaf agent download commands for io.keploy.agent-2.0.2.jar

This PR Resolves # 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).
• Documentation update (if none of the other choices apply).

How Has This Been Tested?

• git diff --check -- versioned_docs/version-4.0.0/keploy-cloud/deduplication.md versioned_docs/version-4.0.0/running-keploy/keploy-karaf.md
• Verified the updated docs reference 2.0.2 for the Maven coordinate and Karaf agent jar.
• Earlier branch validation covered yarn install --frozen-lockfile, yarn build, and Vale checks for the Java SDK installation and deduplication docs.

Related PRs:

• Java SDK agent: feat: run Java dedup as java agent java-sdk#183
• Samples: feat: attach Java dedup agent in sample samples-java#133
• Enterprise CI: https://github.com/keploy/enterprise/pull/1959

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.