fix: handle case-sensitive file overwrite on Windows and add tests

[ana1250]

This PR fixes an issue (#1140) where copying a file with the same name but different casing on Windows resulted in an "already in use" error. It aligns the behavior with the native file system.

Changes

• Fixed file overwrite logic to properly handle case-insensitive paths on Windows.
• Added Windows-specific checks to mimic System.IO.File.CopySystem.IO.File.Move and System.IO.File.Replace behavior.
• Implemented test cases to verify expected behavior for case-sensitive and case-insensitive file systems.
• Ensured that the fix does not affect Linux behavior.

Testing

• Verified that the fix works correctly on Windows by checking file existence before and after copying,moving and replacing file with different cases
• Ran test cases on both Windows and Linux to ensure no unintended side effects.

[vbreuss]

Thanks @ana1250, looks really good.
I just have some minor suggestions on improving the tests...

[github-actions]

This is addressed in release v22.0.13.

[ana1250]

Thanks! Looking forward to contributing more.

[siprbaum]

in all the other cases we use
mockFileDataAccessor.StringOperations.Equals(sourceFileName, destinationFileName) instead of relying on
string.Equals(..., ..., StringComparison.OrdinalIgnoreCase)

Is intentional or an oversight?

[vbreuss]

This seems to be an oversight.
We had one case here where we used string.Equals on purpose, as it should compare case-sensitive in all operating systems, but here it seems I overlooked it.