perf: deploy and retrieve flow efficiency improvements @W-24222996@

[WillieRuemmele]

@W-24222996@

Summary

Collection of targeted performance improvements across SDR's deploy and retrieve flows:

• Avoid materializing lazy collections: Replace getSourceComponents().toArray() with spread syntax in buildFileResponsesFromComponentSet
• Hoist regex literals to module scope: Prevent regex recompilation on every function call in path.ts, metadataResolver.ts, and baseSourceAdapter.ts
• Use composite key for FileResponse dedup: Replace JSON.stringify() with a string key concatenation in getFileResponses
• Use Set for O(1) lookups: Replace linear Array.find() with Set.has() in warnIfUnmatchedServerResult
• Remove redundant statSync guard: Replace statSync + readdirSync with try/catch around readdirSync in NodeFSTreeContainer.readDirectory
• Index ZipTreeContainer directory children: Build a Map<dir, children[]> at construction time instead of O(n) scanning all zip entries on every readDirectory call

Benchmark results

Benchmark	Before	After	Improvement
eda-componentSetCreate	370ms	159ms	57% faster
eda-sourceToMdapi	2438ms	1976ms	19% faster
eda-sourceToZip	2608ms	2105ms	19% faster
eda-mdapiToSource	3284ms	2841ms	13% faster
lotsOfClasses-componentSetCreate	515ms	374ms	27% faster
lotsOfClasses-sourceToMdapi	6125ms	4213ms	31% faster
lotsOfClasses-sourceToZip	7838ms	5916ms	25% faster
lotsOfClasses-mdapiToSource	6150ms	4221ms	31% faster
lotsOfClassesOneDir-componentSetCreate	861ms	493ms	43% faster
lotsOfClassesOneDir-sourceToMdapi	10950ms	7578ms	31% faster
lotsOfClassesOneDir-sourceToZip	14269ms	11612ms	19% faster
lotsOfClassesOneDir-mdapiToSource	11216ms	7839ms	30% faster

Test plan

• All unit tests pass
• All snapshot tests pass
• Build passes with no lint errors
• Performance benchmarks show improvement across all suites

[github-actions]

This PR lacks any commits of the 'fix' or 'feat' type, and therefore will not trigger a release. To silence all further warnings, react to this warning comment (or any other) with the 👀 emoji.

NOTE: If your repo uses squash commits, make sure to add the appropriate conventional commit prefix (e.g., 'fix:', 'feat:', 'chore:', etc) in the squash commit message.