wire up config-driven generic specialization

Configuration.specialize was fully defined (JSON schema, SpecializationConfigEntry,
SwiftAnalyzer.registerSpecialization) but nothing in the actual jextract run
ever read it - translator.analyze() was called with no hook, so a
"specialize": {...} block in swift-java.config silently did nothing.
Pass a hook that registers each entry via registerSpecialization before
deferred constrained extensions are processed, so config-declared
specializations of a generic type (e.g. Snowflake<Tag> -> GuildSnowflake,
ChannelSnowflake, ...) actually produce usable per-instantiation Java classes.

Author: llsc12

Sources/JExtractSwiftLib/Swift2Java.swift

@@ -119,7 +119,20 @@ public struct SwiftToJava {
       translator.sourceDependencies.loadSwiftSources(from: config, log: translator.log)
     }
 
-    try translator.analyze()
+    try translator.analyze { analyzer in
+      for (outputName, entry) in config.specialize ?? [:] {
+        guard
+          analyzer.registerSpecialization(
+            baseQualifiedName: entry.base,
+            outputName: outputName,
+            typeArgs: entry.typeArgs
+          ) != nil
+        else {
+          log.warning("Failed to register configured specialization '\(outputName)' of '\(entry.base)'")
+          continue
+        }
+      }
+    }
 
     switch config.effectiveMode {
     case .ffm: