While looking at #5692, I realised that DocumentLinks would also just find the "first" version of a package: URI to link to, which could be incorrect if a workspace has projects that reference different versions of the same dependency.

We should prefer to look at the package map for the project containing the source file, and only fall back to finding another match if there isn't one.