ref(android): Catch only expected exceptions when parsing profiling config

Narrow the deserialization catch from Throwable to Exception. The vendored JSON
reader signals bad input with IOException (MalformedJsonException, EOFException),
IllegalStateException on token type mismatch, and NumberFormatException on an
unparseable number — all Exception subclasses. Catching Throwable additionally
swallowed Error, which is never a recoverable "config file is bad" signal.

This also restores parity with JsonSerializer.deserialize, which catches
Exception, so the replaced behaviour is matched exactly rather than widened.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: runningcode

sentry-android-core/src/main/java/io/sentry/android/core/SentryPerformanceProvider.java

@@ -172,13 +172,17 @@ private void launchAppStartProfiler(final @NotNull AppStartMetrics appStartMetri
    * them.
    *
    * <p>Returns null on malformed input, matching what {@code JsonSerializer.deserialize} did, so
-   * callers keep reporting it as a deserialization failure rather than a read error.
+   * callers keep reporting it as a deserialization failure rather than a read error. The vendored
+   * JSON reader signals bad input with {@link java.io.IOException} (including {@code
+   * MalformedJsonException} and {@code EOFException}), {@link IllegalStateException} on a token
+   * type mismatch, and {@link NumberFormatException} on an unparseable number — all {@link
+   * Exception} subclasses, so {@code Error} propagates instead of being swallowed here.
    */
   private @Nullable SentryAppStartProfilingOptions deserializeProfilingConfig(
       final @NotNull Reader reader) {
     try (final @NotNull JsonObjectReader jsonReader = new JsonObjectReader(reader)) {
       return new SentryAppStartProfilingOptions.Deserializer().deserialize(jsonReader, logger);
-    } catch (Throwable e) {
+    } catch (Exception e) {
       logger.log(SentryLevel.ERROR, "Error when deserializing", e);
       return null;
     }