NPM: Same dependency, different versions causes failure

[winston]

If there are two NPM dependencies in the deno.lock with varying dependencies, such as

import color from "npm:chalk@5.3.0";
import "npm:chalk@5.2.0";

The build fails. That's because the registry.json symlink that's created last takes precedence. To fix it, I'll have to combine the info of both cached packages.
That will probably have to get handled in the denoCacheRestoreHook, and removed from the mkDenoDir expression.