fix: use name and version properties if present when parsing pnpm.yaml locks

[G-Rath]

When researching how pnpm represents git dependencies in it's lock to support extracting commits, I found out a bit more on how the dependencies paths work.

Turns out pnpm captures the name and version within the dependency path if possible, otherwise it includes them as a property - so if either of those properties are present we should favor them over whatever we extract from the dependency path.

This has also highlighted that this parser is probably the most inaccurate, but I'm not too fussed because it should only be falling over on exotic cases and I've not got a lot of easy reference to confirm what is and isn't correct so for now I'll have to rely on people opening issues if they find something is not being parsed correctly.