fix(core): disable autoReferenced on HotUpdate.Code asmdef

Hot-update assemblies are loaded at runtime by Bootstrap; they should
not be compile-referenced by Unity's predefined assemblies
(Assembly-CSharp, Assembly-CSharp-firstpass). With autoReferenced=true,
any Assembly-CSharp source that uses a HotUpdate.Code.* type embeds a
real assembly reference into Assembly-CSharp's metadata.

During the Unity player build, HybridCLR's FilterHotFixAssemblies
(IFilterBuildAssemblies) correctly strips HotUpdate.Code from the
player staging area. Obfuz's ObfuscationProcess
(IPostBuildPlayerScriptDLLs) then tries to obfuscate Assembly-CSharp
and recursively resolves its assembly refs via AssemblyCache.LoadModule
(Obfuz Editor/Utils/AssemblyCache.cs:75-97). The HotUpdate.Code ref
can't be resolved from the player search paths, so obfuscation throws
FileNotFoundException: Assembly HotUpdate.Code not found.

Setting autoReferenced=false removes the trigger for template users:
Assembly-CSharp no longer auto-references HotUpdate.Code, so nothing
forces the metadata ref, and Obfuz's recursive resolver never asks for
HotUpdate.Code. Verified safe for the current template: PromptInitializer
references only JEngine.Core / JEngine.UI, and AOTGenericReferences.cs
emits HotUpdate.Code.* entries as comments only
(GenericReferenceWriter.cs:72-127).

Signed-off-by: JasonXuDeveloper - 傑 <jason@xgamedev.net>

Author: JasonXuDeveloper

UnityProject/Assets/HotUpdate/Code/HotUpdate.Code.asmdef

@@ -18,7 +18,7 @@
     "allowUnsafeCode": false,
     "overrideReferences": false,
     "precompiledReferences": [],
-    "autoReferenced": true,
+    "autoReferenced": false,
     "defineConstraints": [],
     "versionDefines": [],
     "noEngineReferences": false