fix: add fallback on non hashable errors

[giortzisg]

Description

When checking for infinite recursion, there is a possibility that the error will be non comparable. In those cases we need to add a fallback to compare the error type and message to avoid panicking.

Issues

• resolves: panic: runtime error: hash of unhashable type mongo.CommandError #1112
• resolves: GO-90

[linear]

GO-90 panic: runtime error: hash of unhashable type mongo.CommandError

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.87%. Comparing base (2cf1dc0) to head (d20ebe1).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
exception.go	75.00%	4 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1113      +/-   ##
==========================================
- Coverage   87.01%   86.87%   -0.14%     
==========================================
  Files          56       57       +1     
  Lines        6130     6150      +20     
==========================================
+ Hits         5334     5343       +9     
- Misses        649      657       +8     
- Partials      147      150       +3     

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

[lcian]

It's unfortunate that we have to use reflection but it seems there's no better way to do this.