feat(backtrace): Stop truncating backtraces

[lcian]

Description

Removes backtrace truncation entirely, by removing the ClientOptions field and the whole logic to implement this behavior.
This branch has been tested for grouping changes for all relevant integrations with code that can be found here: https://github.com/lcian/sentry-samples-rust/tree/main/stacktrace-truncation.

Issues

Close #885
Close RUST-100

Next steps

• Remove options from docs if they're there -- ✅ the options were not there in the first place
• Release in a minor

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against ffb2fda

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 73.81%. Comparing base (a57b91c) to head (ffb2fda).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #925   +/-   ##
=======================================
  Coverage   73.81%   73.81%           
=======================================
  Files          64       64           
  Lines        7538     7504   -34     
=======================================
- Hits         5564     5539   -25     
+ Misses       1974     1965    -9     

[cursor]

Bug: Dead configuration option remains in public API

The extra_border_frames field in ClientOptions is no longer used anywhere after removing the backtrace trimming functionality, but it remains in the public API with documentation suggesting it has an effect. Users configuring this option will have their settings silently ignored, creating a confusing developer experience where the configuration appears valid but does nothing.

sentry-core/src/clientoptions.rs#L191-L194

sentry-rust/sentry-core/src/clientoptions.rs

Lines 191 to 194 in e05ce91

	pub session_mode: SessionMode,
	/// Border frames which indicate a border from a backtrace to
	/// useless internals. Some are automatically included.
	pub extra_border_frames: Vec<&'static str>,

 

---

[linear]

RUST-100 Remove unnecessary SDK-side data truncation and rely on Relay for handling max length limits.

[lcian]

Not having this would make a frame (that was previously trimmed away) belonging to sentry_tracing be marked as in-app when reporting errors through tracing::error, hence breaking grouping when done by the "in-app stack trace" algorithm.
This has been detected by my test matrix.

[szokeasaurusrex]

lgtm, I think we can make the changelog a bit more human-readable though :)