Use modern stripping option

[konstin]

Use -C strip=symbols instead of -C link-arg=-s. Still broken due to rust-lang/cargo#14346, but i think it's the right modernization anyway.

[netlify]

✅ Deploy Preview for maturin-guide ready!

Name	Link
🔨 Latest commit	68f297b
🔍 Latest deploy log	https://app.netlify.com/sites/maturin-guide/deploys/66afa5c181aaf60009571fcf
😎 Deploy Preview	https://deploy-preview-2173--maturin-guide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[messense]

LGTM, note that this only supports Rust 1.45+ which should be acceptable.

[edmorley]

Still broken due to rust-lang/cargo#14346, but i think it's the right modernization anyway.

Another option which would both work around the cargo regression and perhaps make things more robust long term would be to switch to setting CARGO_PROFILE_RELEASE_STRIP=true instead of passing manual linker args.

I think passing manual linker args is always going to risk conflicts with Cargo implementation details, whereas using the Cargo provided options (via env vars) will mean Maturin benefits from whatever improvements Cargo makes to features over time (for example, perhaps in the future strip=true might also enable other optimisations, that the manual linker options wouldn't) - plus means Maturin works out of the box more like how end users might invoke Cargo outside of Maturin.