Fix Windows and macOS CI failures by compiling librsync source directly

[Copilot]

Windows and macOS cibuildwheel builds were failing due to:

1. macOS: hardcoded .so extension instead of .dylib
2. Windows: CMake architecture mismatch when building multi-arch wheels (x86/AMD64/ARM64) against single-arch prebuilt library

Changes

• CI workflow: Remove USE-LIB flag so librsync C sources compile directly into the extension, avoiding CMake architecture issues entirely
• setup.py: Add macOS .dylib handling for local --use-lib builds
• Runners: Use macos-13 instead of macos-15-intel; drop riscv64 (limited support)

The cmake step is retained solely to generate config.h which is required by librsync sources.

# Before: tried to link prebuilt library (failed on multi-arch)
CIBW_ENVIRONMENT: USE-CYTHON="1" USE-CFFI="1" USE-LIB="1"

# After: compile sources directly (works for all architectures)
CIBW_ENVIRONMENT: USE-CYTHON="1" USE-CFFI="1"

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Windows and macos ci fails</issue_title>
<issue_description>Linux ci is ok though. Refer https://github.com/synodriver/pyrsync/actions/runs/19860094659/job/56907688409.</issue_description>

<agent_instructions>I can build it on my pc with win10... looks like the ci's environment is strange...</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Windows and macos ci fails #2

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.