fix[thin_wallet]: handle address history invalid tx version

[luislhl]

Motivation

There is an exception not treated when an user inputs invalid tx version in the /address_history endpoint: https://hathor.app.opsgenie.com/alert/detail/6b7fd5dd-05d4-4347-b334-54f662c64fda-1769746499423/details

Acceptance Criteria

• We should capture the exception and return an error response without raising an exception

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged

[github-actions]

Bencher Report

Branch	fix/thin_wallet/address-history-invalid-tx-version
Testbed	ubuntu-22.04

Click to view all benchmark results

Benchmark	Latency	Benchmark Result minutes (m) (Result Δ%)	Lower Boundary minutes (m) (Limit %)	Upper Boundary minutes (m) (Limit %)
sync-v2 (up to 20000 blocks)	📈 view plot 🚷 view threshold	1.67 m (-2.43%) Baseline: 1.71 m	1.54 m (92.24%)	2.06 m (81.31%)

🐰 View full continuous benchmarking report in Bencher

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 85.72%. Comparing base (a98679e) to head (2a9bd2b).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
...or/wallet/resources/thin_wallet/address_history.py	83.33%	1 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1590      +/-   ##
==========================================
+ Coverage   85.68%   85.72%   +0.03%     
==========================================
  Files         442      442              
  Lines       33846    33862      +16     
  Branches     5293     5297       +4     
==========================================
+ Hits        29000    29027      +27     
+ Misses       3824     3817       -7     
+ Partials     1022     1018       -4     

Flag	Coverage Δ
test-lib	85.72% <83.33%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[raul-oliveira]

Both error responses return 200 with success: False. Consider returning 400 Bad Request for invalid parameters, which is more semantically correct for client errors.