CrashReport production config file

[LukasKorba]

The crash reporter is using a Firebase and needs to be properly setup in order to work. The configuration file is called GoogleService-Info.plist and production version of this file holds production ID.

Pacu implemented some way how to use a dummy file for the development and for the reason of OSS so the ID is not visible to anyone. I don't recall the production side of it but my understanding is that the production config file was added to the project as part of the production release on the CI side. Probably Bitrise(?) was used for this. The dummy was was replaced by the production one holding the right values, built and distributed to the testflight. In this process the ID is never leaked.

Since we started over and have a new bitrise account we lost all this so the crash reporter is technically not working but all code is in place. The right config file is needed in order to have the functional crash reporting.

[pacu]

@LukasKorba What we did was to inject the testnet or mainnet plist file at build time using bitrise similarly as Android does with GitHub Actions.

[LukasKorba]

The release build doesn't work because of this script. Removing it for now as a solution for #779

# Type a script or drag a script file from your workspace to insert its path.
if [[ $UPLOAD_CRASHLYTICS_SYMBOLS = "NO" ]]; then
   echo "DEBUG BUILD: SKIPPING UPLOAD SYMBOLS STEP"
else
${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run
fi