Fixed Maven publishing

- ItemsAdder API resolves from Maven Central
- Integration repositories only resolve their assigned groups and modules
- Shared VolmLib classes and packaging use the same pinned revision
- JitPack builds and publishes with remote dependencies
- Local Maven publication uses art.arcane:iris with the configured version
- API generation tracks the final archive filename lazily
- API jars retain signatures and metadata with valid throwing method stubs
- Publication tests verify metadata, bytecode, and consumer compilation

adapters/neoforge/build.gradle

@@ -32,7 +32,11 @@ buildscript {
         maven { url = uri('https://jitpack.io') }
     }
     dependencies {
-        classpath('com.github.VolmitSoftware.VolmLib:packaging:master-SNAPSHOT')
+        Properties libraryProperties = new Properties()
+        file('../../gradle.properties').withInputStream { InputStream stream -> libraryProperties.load(stream) }
+        String libraryCoordinate = providers.gradleProperty('volmLibCoordinate')
+            .getOrElse(libraryProperties.getProperty('volmLibCoordinate'))
+        classpath("com.github.VolmitSoftware.VolmLib:packaging:${libraryCoordinate.tokenize(':').last()}")
     }
 }