SrgToMcpRenamer uses hardcoded path for nested jars

src/main/java/net/minecraftforge/installertools/SrgMcpRenamer.java の132行目付近を調べ、続いてリンクされている JarJar メタデータ定義を読んで、ネストされた JAR のパスが外側の JAR を基準にどのように表現されるかを理解します。SrgToMcpRenamer がそのメタデータパスを読み取り、META-INF/jarjar/ を前提とせず、場所に関係なくネストされた JAR をデオブファスケートできれば完了です。

The Issue

Currently, only nested jars under the META-INF/jarjar/ directory are deobfuscated by SrgToMcpRenamer.

https://github.com/MinecraftForge/InstallerTools/blob/dd66a7d92e635e654ad356b7a18e56149e339539/src/main/java/net/minecraftforge/installertools/SrgMcpRenamer.java#L132

While this is the most common folder for nested jars, JarJar metadata defines nested jar paths as paths relative to the outer jar's root, and therefore nested jars can be located anywhere in the jar. This breaks mods that place their nested jars in other paths than the mentioned folder.

Expected behavior

SrgToMcpRenamer is able to deobfuscate any nested jars regardless of their location, as specified by JarJar metadata. Rather than assuming all nested jars are in the META-INF/jarjar/ directory, we should open the jar's JarJar metadata file and read nested jar paths from it.