chore(crashlytics): refactor deprecation implementation

[russellwheatley]

Description

• Use a proxy on each module instance, allows us to have all deprecation warnings in one place and to keep a map of deprecated methods and the corresponding modular method if available.
• For testing, I have mocked the underlying FirebaseModule and proxied every get request on native object which should hopefully speed up writing tests. I had a battle on firestore unit tests mocking the query instance, and this should make it a lot easier.
• Also updated tests to check the actual message is correct and properly cleared the jest spy as it was being polluted by firebase app() invocation.

Related issues

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 22, 2024 1:23pm