Disable Crashlytics and Analytics data collection in debug builds

[diveshpatil9104]

fixes #632

Summary

Debug builds are currently sending crash reports and analytics events to Firebase, creating noise in the production Crashlytics dashboard. This PR disables data collection in debug builds.

Problem

FirebaseApp.configure() in FirebaseAnalytics.init runs unconditionally for all build configurations. This means every simulator run and debug session sends data to Crashlytics, making it harder to identify real user crashes in the Firebase console.

Fix

Added a #if DEBUG block after FirebaseApp.configure() that disables both Crashlytics and Analytics collection:

#if DEBUG
Crashlytics.crashlytics().setCrashlyticsCollectionEnabled(false)
Analytics.setAnalyticsCollectionEnabled(false)
#endif

Firebase is still configured (preventing crashes from unconfigured Firebase calls), but no data is collected or transmitted in debug builds.

Testing

• Verified debug builds no longer send crash reports to Firebase console

[aaronbrethorst]

Hey Divesh — clean surgical fix. The #if DEBUG placement is correct: it runs after FirebaseApp.configure() (so Firebase doesn't crash from being unconfigured) but before Analytics.setUserID (which becomes a no-op once collection is disabled). I verified that setReportingEnabled(_:) only toggles Analytics, not Crashlytics, so the Crashlytics disable stays in effect for the entire debug session. And the only call site for setReportingEnabled is SettingsViewController, meaning a developer would have to deliberately re-enable analytics from the Settings UI — that's perfectly acceptable.

This looks good to merge. Thanks for keeping the production dashboards clean!