Clean up speculative Sentry logging

[fredrikekelund]

Related issues

• Fixes STU-1478

How AI was used in this PR

N/A

Proposed Changes

In #2793, we implemented a data migration from the old appdata-v1.json config file to the new decoupled file strategy (living in ~/.studio). During that data migration, we added Sentry logging to help us catch certain types of errors.

Per pfHvTO-1ct-p2, we want to avoid leaving this kind of "speculative logging" in the code for longer periods of time, so this PR removes the Sentry.captureException calls. These errors would only have occurred if the appdata-v1.json file didn't conform to the expected schema. Luckily, we didn't catch any such errors.

Testing Instructions

Code review is sufficient

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wojtekn]

Looks good, thanks for the claenup.

[wpmobilebot]

📊 Performance Test Results

Comparing a917849 vs trunk

app-size

Metric	trunk	a917849	Diff	Change
App Size (Mac)	1334.65 MB	1334.65 MB	0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	a917849	Diff	Change
load	1680 ms	1659 ms	21 ms	⚪ 0.0%

site-startup

Metric	trunk	a917849	Diff	Change
siteCreation	9003 ms	9056 ms	+53 ms	🔴 0.6%
siteStartup	4420 ms	4401 ms	19 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)