ref(ci): Split and upload debug info to Sentry

[jan-auer]

The release binary included debug info (debug = true) for local symbolication of stack traces, but this produces large binaries and Docker images.

The CI build now splits debug info out of the binary using llvm-objcopy, strips the binary, and bundles sources with sentry-cli. Both the debug zip and source bundle are uploaded to GCS alongside the existing release-name, and the Docker image ships the smaller stripped binary.

At deploy time, the GoCD create-sentry-release script downloads the debug info and source bundle for both platforms and runs sentry-cli upload-dif before creating the Sentry release, so production stack traces can be symbolicated.

The local cross-build script also disables debug info by default to reduce upload size for sandbox builds. CARGO_PROFILE_RELEASE_DEBUG=true re-enables it.

Fixes FS-444

[codecov]

Codecov Report

❌ Patch coverage is 99.31034% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 87.53%. Comparing base (e88b7f8) to head (07848d8).

Files with missing lines	Patch %	Lines
objectstore-service/src/streaming.rs	98.21%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #573      +/-   ##
==========================================
- Coverage   87.67%   87.53%   -0.15%     
==========================================
  Files          93       93              
  Lines       15113    14969     -144     
==========================================
- Hits        13251    13103     -148     
- Misses       1862     1866       +4     

Components	Coverage Δ
Rust Backend	92.34% <99.31%> (-0.11%)	⬇️
Rust Client	79.89% <ø> (ø)
Python Client	90.20% <ø> (ø)

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[linear-code]

FS-444