docs: crash reporting docs

[ShootingStar91]

✨ What has changed?

Added docs for crash reporting with basic description of what you find from sentry, and tips on how to send custom errors and messages.

IOS part is left as TODO as I haven't touched Apple Store so I don't know what's there.

[github-actions]

Hi! 👋

To ensure a smooth review process, it is recommended to trigger a build (or an update if no native changes have been made since the last build).

You can do so by applying the appropriate label based on your needs:

• 🏗️ 🍏 iOS Build: Select eas-build-ios:dev to trigger a build for iOS
• 🏗️ 🤖 Android Build: Select eas-build-android:dev to trigger a build for Android
• 🏗️ 📲 All Platforms Build: Select eas-build-all:dev to trigger builds for both platforms
• 🌐 EAS Update: Select eas-update to trigger an update (automatically for both platforms)

Note

The update is managed by a custom GitHub action, while the build actions are handled directly via EAS integration.

Once you apply the respective label, the appropriate workflow will be triggered automatically. You can monitor the progress in the Actions tab.

Warning

If you push new commits to your PR branch after selecting a build label, a new build will be triggered automatically.

It is advisable to remove the label once applied and reapply it if necessary; you will likely need to trigger an update instead of a fresh build.

Important

After merging changes into the dev branch, a build will automatically be triggered for both platform using the dev profile.

Therefore, there is no need to manually initiate a build after merging to the dev branch.

Additionally, builds will automatically trigger when promoting changes to dev, test and prod.

For the prod branch, the build will also be automatically submitted to the app stores.

For more information, refer to the PR Reviews Guide.

[JulienTexier]

LGTM