Mod ID resolution for loader_dependencies overrides

[sisby-folk]

Hey gang, I've bumped up against the quilt_loader_dependencies.json implementation and while the ability to specify mod path increases the accuracy of how the dependency change is applied, it makes it straight useless for use cases that work great in fabric.

Here's an example - we maintain a modpack that contains MemoryLeakFix - every update, memory leak fix bumps the required floader version to the absolute latest. As expected, this breaks our quilt pack half the time because the embedded floader version in qloader is a little out of date.

Easy solution - target the mod with ID memoryleakfix and just totally remove the fabricloader dependency, then completely forget about the issue and freely update memoryleakfix whenever you want.

Problem - dependency overrides can only target by paths. Paths change every mod update. For modpack development that runs live and updates with the mods inside, this seems to fall a bit flat - I'm better off just disabling updates for the mod entirely. Seems like being able to use either a path key or an id key would resolve this.