Optimize EnforceResetValues: unconditional reset is 11-39% faster

[konard]

Summary

This PR optimizes the EnforceResetValues method based on performance analysis that shows unconditional reset is 11-39% faster than conditional reset.

Problem

Issue #159 asked: "What is faster: to write unconditionally or write only when required?" before link deletion.

The original implementation used a conditional approach:

if (!links.AreValuesReset(linkIndex))
{
    return links.ResetValues(linkIndex, handler);
}
return links.Constants.Continue;

Solution

Changed to unconditional approach:

return links.ResetValues(linkIndex, handler);

Performance Results

Benchmark with 50,000 operations on 100 links:

Scenario	Conditional	Unconditional	Improvement
Links with values	1,251 ms	762 ms	39.1% faster
Links already reset	86 ms	76 ms	11.6% faster

Why It's Faster

1. Eliminated overhead of AreValuesReset() which calls GetLink() and compares values
2. Reduced branch prediction penalties from conditional logic
3. Simpler control flow - direct path to reset operation
4. Update() is optimized for null value operations

Files Changed

• csharp/Platform.Data.Doublets/ILinksExtensions.cs - Optimized EnforceResetValues method
• PERFORMANCE_ANALYSIS.md - Detailed benchmark results and analysis

Test Plan

• Benchmarked both approaches extensively
• Verified builds pass with no compilation errors
• Confirmed existing functionality remains intact
• Performance improvement validated in both scenarios

The unconditional approach is clearly superior in all tested scenarios.

🤖 Generated with Claude Code

---

Resolves #159