Track non-fatal issues via analytics / Sentry if consent provided

[Anderas]

Adds Sentry as a monitoring tool to track app health metrics such as crashes and non-fatal issues logged via MXLog.failure. Using Sentry is subject to the same user consent as other crash and analytics data and is configurable from user settings.

Sentry in this PR is integrated directly into an existing Analytics class, which has some pros:

• the rest of the application does not need to understand the difference between PostHog and Sentry, Analytics merely serves as façade
• existing code related to starting / stoping / optingIn / optingOut of analytics would have to be duplicated in all places, if Sentry was another top-level service

The downside of this approach is giving Analytics more responsibilities than it was originally indented to have. I tried to remedy this by changing the documentation of the class, but it is still overwhelmingly aimed at tracking AnalyticEvents. Further refactors could make the split between the use cases more explicit.

Related SDK change

[ismailgulek]

One inline comment, otherwise LGTM!

[ismailgulek]

I wonder if SentrySDK.endSession makes more sense here. Not sure but feels like close is an unrecoverable action.

[Anderas]

endSession only really rotates session IDs etc, but keeps the Sentry service running. Having tested this out close is not in fact unrecoverable and SentrySDK can be properly restarted again.

[gileluard]

lgtm

[github-actions]

📱 Scan the QR code below to install the build for this PR.
🔒 This build is for internal testing purpose. Only devices listed in the ad-hoc provisioning profile can install Element Alpha.

If you can't scan the QR code you can install the build via this link: https://i.diawi.com/viHKYU

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[codecov-commenter]

Codecov Report

Merging #6308 (0dea010) into develop (40e927a) will increase coverage by 0.00%.
The diff coverage is 2.38%.

@@           Coverage Diff            @@
##           develop    #6308   +/-   ##
========================================
  Coverage     6.23%    6.23%           
========================================
  Files         1443     1444    +1     
  Lines       155488   155533   +45     
  Branches     62484    62502   +18     
========================================
+ Hits          9695     9699    +4     
- Misses      145386   145427   +41     
  Partials       407      407           

Impacted Files	Coverage Δ
...iot/Modules/Analytics/SentryMonitoringClient.swift	0.00% <0.00%> (ø)
Riot/Modules/Analytics/Analytics.swift	9.81% <14.28%> (+0.15%)	⬆️
...ojiPicker/Data/EmojiMart/EmojiItem+EmojiMart.swift	95.65% <0.00%> (+0.30%)	⬆️

---

Continue to review full report at Codecov.

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