fix: address false negatives in Java/Kotlin patterns

[avifenesh]

Summary

Follow-up to #21 and #22. A 5-agent team tested all Java/Kotlin patterns against 6 real-world repos (1955 files) hunting for false negatives - code that IS slop but wasn't caught.

Pattern improvements (7)

Pattern	Change	Why
java_sysout_debugging	Add printf, format, write, append	Only caught print/println
java_suppress_warnings	Add array {...} and value= forms	Only caught simple string form
java_raw_type	Add HashMap, ArrayList, TreeMap, LinkedList, ConcurrentHashMap, Vector, Stack, etc.	Only caught interface types
kotlin_println_debugging	Also catch print() without ln	print() is equally debug output
kotlin_swallowed_error	Catch getOrDefault(null) and getOrElse { null }	Same swallowed-error semantics as getOrNull()
kotlin_suppress_annotation	Catch multi-value @Suppress("A", "B") and @file:Suppress	Only caught single-value declaration-level

New pattern (1)

Pattern	What it catches	Found in
kotlin_android_debug_log	Log.d/v/i() Android logging	6 instances in nowinandroid

Test repos used

Repo	Type	Files
spring-petclinic	Java corporate	47
spring-authorization-server	Java corporate	468
nowinandroid	Kotlin mobile	351
Pokedex	Kotlin mobile	66
gson	Java lib	261
Exposed	Kotlin lib	762

Test plan

• 2127 tests passing (all suites)
• 39/39 synthetic edge case checks pass
• Based on false-positive tuning branch (fix: tune Java/Kotlin patterns to reduce false positives #22)

Depends on #22