Materialize outputs after recursively memoized cache hits

src/Common/MSBuildCachePluginBase.cs を読み、ConcurrentDictionary<NodeContext, Lazy<Task>> の再帰的な結果パスと、materializeOutputs の扱いに注目してください。再帰的なクエリと直接のクエリを追跡し、その後、依存関係クエリの順不同実行と multi-targeting の inner build を対象とする、決定論的な並行性／順序テストを追加してください。再帰的で materialize を行わないヒットによって必要な出力が正確に 1 回だけ materialize され、デフォルトの動作と非再帰的な動作が変更されないことが完了条件です。

Summary

Recursive cache results are memoized only by NodeContext, but each memoized Lazy<Task<CacheResult>> captures whether outputs should be materialized.

Impact

With MSBuildCacheGetResultsForUnqueriedDependencies=true, a recursive query that does not require outputs can populate the memoized result first. A later direct query for the same node reuses that cache hit without materializing required files, allowing MSBuild to proceed with missing reference assemblies or other outputs.

Evidence

src/Common/MSBuildCachePluginBase.cs stores recursive results in ConcurrentDictionary<NodeContext, Lazy<Task<CacheResult>>>. materializeOutputs is not part of the key or separately tracked. The implementation comments assume the node will not later be queried directly, while the setting is documented for builds that are not executed in graph order.

Suggested fix

Separate result lookup from materialization state. A direct caller requiring outputs should be able to materialize a previously memoized non-materialized hit without repeating fingerprint/cache lookup. Alternatively, include the materialization requirement in memoization while preventing duplicate result mutation.

Acceptance criteria

• A recursive non-materializing hit followed by a direct query materializes outputs exactly once.
• The fix covers out-of-order dependency queries and multi-targeting inner builds.
• Default and non-recursive behavior remains unchanged.
• A deterministic concurrency/order test covers the regression.