Support local Forge/NeoForge patched Minecraft jars

[F1reW4tch]

Why patched Minecraft jars is needed

Forge/NeoForge have heavily patched Minecraft classes, the most common patches are adding new methods with more params and deprecating the vanilla one. For Forge/NeoForge mods, using these patched method is the best practice for the sake of compatibility, so it's important to provide the patched code for the agent.

How should patched Minecraft jars work

Patched Minecraft jars should work as different versions of Minecraft, and the version will be provided by the user upon introducing the jar with decompile_minecraft_version (since loader version can't be inferred from the patched jar), the conventional version schema could be <mc version>-<loader>-<loader version>.

Current workaround without patched Minecraft jar support

While not intuitive, agents could be told to use the mod jar tools to decompile and search patched Minecraft code since these tools supports local jars.

[GhostTypes]

I've added initial support for this following your suggested schema, and will create a new release / version after I finish testing / make sure all is good

If you're able to do a local install (changes are not on npm yet) to verify everything works as expected , that would be great 😄
I plan to finalize testing tomorrow afternoon/evening as time allows

[GhostTypes]

@F1reW4tch Any update on this? I can push the changes to npm , just wanted to have you verify first if possible

Everything is working as expected on my end 👍