Fix natural numeric ordering for chunks beyond Int32 range

[Copilot]

NaturalStringComparer treated large digit runs as plain strings when int.TryParse overflowed, which inverted ordering for values like 9999999999 vs 10000000000. This change makes numeric chunk comparison size-unbounded and adds a regression case at the Int32 boundary.

• Comparer logic

  • Replaced int.TryParse-based numeric comparison with digit-chunk comparison that:
    • trims leading zeros
    • compares normalized chunk length first
    • falls back to ordinal digit comparison when lengths match
  • Preserves natural numeric ordering for arbitrarily large numeric substrings.

• Regression coverage

  • Extended Compare_LargeNumbers_HandledCorrectly with a boundary-crossing case:
    • "file9999999999" sorts before "file10000000000".

private static int CompareNumericChunks(string xChunk, string yChunk)
{
    string xTrimmed = xChunk.TrimStart('0');
    string yTrimmed = yChunk.TrimStart('0');

    if (xTrimmed.Length == 0) xTrimmed = "0";
    if (yTrimmed.Length == 0) yTrimmed = "0";

    int lengthComparison = xTrimmed.Length.CompareTo(yTrimmed.Length);
    if (lengthComparison != 0) return lengthComparison;

    return string.Compare(xTrimmed, yTrimmed, StringComparison.Ordinal);
}

• Fixes NaturalStringComparer mis-orders numeric chunks of 10+ digits due to Int32 overflow fallback #41

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud