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

gradle.properties

@@ -30,4 +30,4 @@ apiVersion=26.1
 fabricLoaderVersion=0.19.3
 forgeVersion=26.2-65.1.1
 neoForgeVersion=26.2.0.59
-volmLibCoordinate=com.github.VolmitSoftware:VolmLib:master-SNAPSHOT
+volmLibCoordinate=com.github.VolmitSoftware.VolmLib:volmlib-shared:6c54bbcd19282508364794df1eacb9720d94a896