Always record call_trace

[emmiegit]

As noted in discussion on #2701, the call_trace field will be retained internally only, and so it is safe to record the data even in the case of authentication issues. (This is because only developers will be reviewing the logs and it cannot be used by attackers to determine internal authentication state).

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 2.09%. Comparing base (eee676d) to head (07606f8).

Files with missing lines	Patch %	Lines
deepwell/src/error/convert.rs	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #2702   +/-   ##
=======================================
  Coverage     2.09%   2.09%           
=======================================
  Files          190     190           
  Lines        12204   12202    -2     
=======================================
  Hits           256     256           
+ Misses       11948   11946    -2     

Files with missing lines	Coverage Δ
deepwell/src/error/convert.rs	0.00% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Zokhoi]

Hmm, I'm not familiar with the relevant code in deepwell, but I believe right now we don't have code to block showing call_trace in production, so maybe reserve this for later?

[emmiegit]

That's fine, we aren't in any rush to merge this.