fix: use the new recommended way to manually crash

[mars-lan]

Description

assert(no) was the original method recommended by Firebase but it turns out that it doesn't actually work (see firebase/firebase-ios-sdk#6028 for more detail). They've subsequently updated the official doc:
https://firebase.google.com/docs/crashlytics/test-implementation?platform=ios

Related issues

While no fixing #4026 completely, it's one step closer.

Release Summary

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[mikehardy]

This is fantastic, thank you - seriously. Lots of users pulling hair out on this issue and this is one step closer yes

[mikehardy]

e2e errors are unrelated, I'm investigating them separately but will merge this shortly either way and kick out a release on this one

[mars-lan]

This is fantastic, thank you - seriously. Lots of users pulling hair out on this issue and this is one step closer yes

Here's another potential pitfall: #3902