Fix infinite config correction loop for scarfOpacity

TOML parses all floating-point values as Double, but scarfOpacity was
defined as Float (0.4f). NeoForge's config validator sees the type
mismatch (Double != Float), rewrites the file, the FileWatcher detects
the write, re-validates, finds it wrong again — infinite loop every 2s.

Changed scarfOpacity from Float to Double to match TOML's native type.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Russell Harland

src/main/java/com/sammy/malum/config/ClientConfig.java

@@ -28,9 +28,9 @@ public class ClientConfig extends LodestoneConfig {
     public static ConfigValueHolder<Integer> SCARF_LENGTH = new ConfigValueHolder<>(MALUM, "client/scarf", (builder ->
             builder.comment("How long should the Malignant Stronghold Scarf be? This value will affect all rendered scarves, not just the one worn by the local player.")
                     .define("scarfLength", 30)));
-    public static ConfigValueHolder<Float> SCARF_OPACITY = new ConfigValueHolder<>(MALUM, "client/scarf", (builder ->
-            builder.comment("How visible. should the Malignant Stronghold Scarf be in first person?")
-                    .define("scarfOpacity", 0.4f)));
+    public static ConfigValueHolder<Double> SCARF_OPACITY = new ConfigValueHolder<>(MALUM, "client/scarf", (builder ->
+            builder.comment("How visible should the Malignant Stronghold Scarf be in first person?")
+                    .define("scarfOpacity", 0.4d)));
 
     public static ConfigValueHolder<Boolean> PARALLEL_WORLD = new ConfigValueHolder<>(MALUM, "client/renderpass", (builder ->
             builder.comment("Enable or disable the parallel world renderer, used for various effects related to a certain feature. Disable if it causes framerate issues.")