chore(IT Wallet): [SIW-2022] Increased serialization for unexpected errors during eID issuance

[RiccardoMolinari95]

Short description

This PR aims to enhance the reason, in the Mixpanel tracking, for errors during eID issuance that fall under IssuanceFailureType.UNEXPECTED .

Some unexpected errors in the reason field on Mixpanel report as {"jsEngine":"hermes"}. Unfortunately, this error is not descriptive, making it difficult to understand what the actual issue was.

List of changes proposed in this pull request

• Added a check within the trackItwIdRequestUnexpectedFailure function to verify if failure.reason is empty
  If failure.reason is empty, the serializeFailureReason function (already used in the useItwFailureSupportModal hook) is utilized; otherwise, the current behavior is maintained.

How to test

Testing with Non-Empty Object

• Using io-react-native-wallet package locally, you can simulate an unexpected error by throwing
  throw new AuthorizationIdpError("access_denied", "ErrorCode nr21: Timeout during user authentication");
• The error is unexpected and the reason is the same before and after the change
  {"code":"ERR_IO_WALLET_IDENTIFICATION_RESPONSE_PARSING_FAILED","error":"access_denied","errorDescription":"ErrorCode nr21: Timeout durante l'autenticazione utente","jsEngine":"hermes","name":"AuthorizationIdpError"}

Testing Serialization Enhancement

• I was able to replicate the situation described in the support tickets using Charles Proxy, where the error was Network request failed. In detail, the error appears as {"reason": [TypeError: Network request failed], "type": "UNEXPECTED"}. Previously, this error was reported on Mixpanel with the reason as {"jsEngine":"hermes"}.
• This type of error, along with others in Mixpanel that have {“jsEngine”: “hermes”} as reason, probably has an empty object as failure.reason, but failure.reason.message is populated. With the recent changes, the reason on Mixpanel should now correctly show the reason

[github-actions]

PR Title Validation for conventional commit type

✅ All good! PR title follows the conventional commit type.

[github-actions]

Jira Pull Request Link

This Pull Request refers to Jira issues:

• SIW-2022

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 51.04%. Comparing base (99a2fbc) to head (9c80283).
Report is 4 commits behind head on master.

Files with missing lines	Patch %	Lines
...es/itwallet/issuance/hooks/useEidEventsTracking.ts	0.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6770      +/-   ##
==========================================
+ Coverage   41.94%   51.04%   +9.10%     
==========================================
  Files        1429     1583     +154     
  Lines       29960    32723    +2763     
  Branches     6662     7355     +693     
==========================================
+ Hits        12566    16703    +4137     
+ Misses      17364    15973    -1391     
- Partials       30       47      +17     

Files with missing lines	Coverage Δ
...es/itwallet/issuance/hooks/useEidEventsTracking.ts	5.26% <0.00%> (-0.99%)	⬇️

... and 448 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e88f105...9c80283. Read the comment docs.

[gispada]

If there is no failure.reason does it make sense to call serializeFailureReason? There should be nothing to serialize.

And do we really need to cast as object?