perf: DebugStackTrace no longer creates a stack trace for dynamic methods

[jamescrosswell]

resolves: #4939

#skip-changelog

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 73.88%. Comparing base (c13180b) to head (e7842e7).
⚠️ Report is 17 commits behind head on main.

Files with missing lines	Patch %	Lines
src/Sentry/Internal/DebugStackTrace.cs	83.33%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4954   +/-   ##
=======================================
  Coverage   73.88%   73.88%           
=======================================
  Files         496      496           
  Lines       17951    17954    +3     
  Branches     3516     3517    +1     
=======================================
+ Hits        13263    13266    +3     
- Misses       3826     3827    +1     
+ Partials      862      861    -1     

☔ View full report in Codecov by Sentry.
📢 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.

[Flash0ver]

question: I guess it's not too easy - or better to say "economic" - to add a unit test for this, right?

[jamescrosswell]

It could possibly be done. This isn't really a functional change though (it doesn't change the behaviour of our SDK)... it's more of a performance change. We're avoiding using exceptions for control flow here and the need to create stack traces for those exceptions.

Given that it's not a functional change, I think a unit test would be overkill... And we could create a benchmark but, again, kind of pointless since we know it's going to be quicker than the previous/alternative code.