Switch to external mapping of detected circular dependencies

[karlhorky]

Thanks for this project, useful to check out how configuration of circular-dependency-plugin is being used in Next.js projects!

Currently, circular dependencies are logged by the config in next-circular-dependency, but the final onEnd callback will show No circular dependencies found:

♻️ Circular dependency detected: server/a.ts -> server.b.ts -> server/c.ts -> server/a.ts
♻️ Circular dependency detected: server.b.ts -> server/c.ts -> server/a.ts -> server.b.ts
✅ No circular dependencies found in server

Switching to the external tracking of compilation.name -> arrays of the detected dependency messages resolves the issue:

♻️ Circular dependency detected: server/a.ts -> server.b.ts -> server/c.ts -> server/a.ts
♻️ Circular dependency detected: server.b.ts -> server/c.ts -> server/a.ts -> server.b.ts
❌ 2 circular dependencies found in server