Refactor FXIOS-15402 [Sentry] Update to 0.9.10 & disable network breadcrumbs

[mattreaganmozilla]

📜 Tickets

Jira ticket
Github ticket

💡 Description

Still investigating but wanted to get a PR up so we have a place to discuss & document. This PR updates Sentry to 0.9.10 and disables breadcrumb logging. We're already disabling enableCaptureFailedRequests 🤔 , the only other culprit I could find was enableNetworkBreadcrumbs. However the documentation states that since network breadcrumbs requires swizzling, the fact that we set enableSwizzling to false should've meant we're not sending breadcrumbs.

📝 Checklist

• I filled in the ticket numbers and a description of my work
• I updated the PR name to follow our PR naming guidelines
• I ensured unit tests pass and wrote tests for new code
• If working on UI, I checked and implemented accessibility (Dynamic Text and VoiceOver)
• If adding telemetry, I read the data stewardship requirements and will request a data review
• If adding or modifying strings, I read the guidelines and will request a string review from l10n
• If needed, I updated documentation and added comments to complex code

[mobiletest-ci-bot]

🧹 Tidy commit

Just 1 file(s) touched. Thanks for keeping it clean and review-friendly!

💬 Description craftsman

Great PR description! Reviewers salute you 🫡

✅ New file code coverage

No new file detected so code coverage gate wasn't ran.

Generated by 🚫 Danger Swift against a206532

[lmarceau]

I checked and we're kind of outdated as well with the Sentry versions. Latest one is 9.10.0 and we are on 8.36.0. The documentation could be untrue for the 8.36.0 version? It's probably worth upgrading the version as well. What do you think?

[lmarceau]

Documentation link is enableNetworkBreadcrumbs

[mattreaganmozilla]

I checked and we're kind of outdated as well with the Sentry versions. Latest one is 9.10.0 and we are on 8.36.0. The documentation could be untrue for the 8.36.0 version? It's probably worth upgrading the version as well. What do you think?

8.36 is surprisingly old. Do we have a formal process for upgrading these types of packages? I'm assuming we use Exact version to avoid unexpected changes, but that also would mean if we decide to update we'll probably need to perform some smoketesting by the Eng team and reach out QA for regression testing? I can coordinate that if we think it's a good time to update.