Add SubtractSaturating extension method for TimeSpan

[Copilot]

Implemented SubtractSaturating method for TimeSpan extensions with comprehensive testing and XML documentation.

• Explored repository structure and understand codebase
• Built and tested existing code to confirm working state (550 tests pass)
• Analyzed existing SafeAdd/SafeSubtract patterns in DateTime extensions
• Implement SubtractSaturating method in TimeSpanExtensions
• Create comprehensive tests for the new method
• Verify implementation follows existing patterns and conventions
• Run all tests to ensure no regressions (558 tests pass)
• Manual verification with test program confirms correct behavior
• Add XML documentation to SubtractSaturating method
• Refactor tests to follow MethodName_StateUnderTest_ExpectedBehavior naming convention

The SubtractSaturating method subtracts one TimeSpan from another and ensures the result doesn't go below TimeSpan.Zero. This implements saturating arithmetic for TimeSpan subtraction, preventing negative results.

Key features:

• Returns self.Subtract(other) when self >= other
• Returns TimeSpan.Zero when result would be negative
• Handles edge cases including zero values and negative TimeSpan inputs
• Follows existing code patterns and naming conventions
• Comprehensive test coverage with 8 focused test methods following best practices
• Complete XML documentation following project conventions

Fixes #43.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[niemyjski]

@copilot add xml documentation

[Copilot]

Added comprehensive XML documentation to the SubtractSaturating method following the project's documentation standards. The documentation includes a summary, parameter descriptions, and return value description. Commit: 91c1ff8

[niemyjski]

@copilot follow my best practices for test naming

[Copilot]

Refactored the test to follow the MethodName_StateUnderTest_ExpectedBehavior naming convention as specified in the testing guidelines. Split the single monolithic test into 8 focused test methods, each testing a specific scenario with descriptive names and proper AAA structure. Commit: aef0ed9