feat: single-linked list for resolver stack

[dmichon-msft]

Improve performance of doResolve by representing the resolver stack via a singly-linked list instead of a Set<string>. Profiling indicated that a significant amount of time was spent cloning resolveContext.stack during doResolve; replacing with a singly-linked list reduces the total memory footprint and makes adding a new entry be O(1) in both time and memory, in exchange for making the circularity check be O(n).

Additionally, this avoids allocating strings for the formatted stack until required when logging it.

Local profiling showed a reduction from 2400ms of self time in doResolve to 88ms of self time plus 73ms for the cost of hasStackEntry, a net reduction of 2239ms.
Measured on NodeJS 18.19.1.

Note that this is a breaking change that will require an update to webpack's ResolverCachePlugin.

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

lib/Resolver.js:748

• [nitpick] The error message string might be unclear. Consider updating it to provide more context about the recursion.

"Recursion in resolving\nStack:" + formatStack(stackEntry)