feat(analytics): Adding default event parameters

[MFrat]

Description

Adding feature for setting default event parameters. As described here in Firebase docs.

Release Summary

Added setDefaultEventParameters. It adds default event parameters that will be send in every event.

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

[CLAassistant]

All committers have signed the CLA.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/invertase/react-native-firebase/DM1PTs437jDP8xcXjef2GuQpi75W
✅ Preview: https://react-native-f-git-fork-mfrat-feature-default-parameters-d30d9d.vercel.app

[mikehardy]

Wow, this looks fantastic first shot. Thank you!
Github requires that a maintainer approves the CI runs on first contributions (to avoid PRs that just implement a cryptominer I think) - so I've done that and will wait for CI to go green

Looks like other than that you just need to follow the "Details" link on the failing CLA / license check and sign the license then we can merge this

[mikehardy]

Oh - now that CI has run it looks like some trivial formatting issues, and the jest error message isn't quite as expected as well as the CLA - waiting for those

[codecov]

Codecov Report

Merging #5246 (1efca6c) into master (3396da2) will increase coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head 1efca6c differs from pull request most recent head 4848a41. Consider uploading reports for the commit 4848a41 to get more accurate results

@@            Coverage Diff             @@
##           master    #5246      +/-   ##
==========================================
+ Coverage   88.86%   88.87%   +0.01%     
==========================================
  Files         109      109              
  Lines        3743     3746       +3     
  Branches      360      361       +1     
==========================================
+ Hits         3326     3329       +3     
  Misses        370      370              
  Partials       47       47              

[MFrat]

Thanks for the tips. Done!

[mikehardy]

Looks like there is still an issue with the CLA signing - I have had this happen before where I needed to add the email address as it mentions:

Max Fratane seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

It appears to be looking for yoru max2fratane @ popular mail provider email address as that's the address in the commits on your fork

[MFrat]

E-mail added to my github account.

[mikehardy]

Hey @MFrat - before I merge this, since it seemed like the iOS side had compile errors and couldn't have been checked - can you install the auto-generated patch-package format patches from CI and make sure they work in your project, with expected results on android and iOS? There is an artifacts link here that has them https://github.com/invertase/react-native-firebase/actions/runs/803147844

[MFrat]

@mikehardy, I tested both in Android and iOS, with devices and simulator/emulator. Everything is working just fine.

Android

iOS

[mikehardy]

That's glorious :-), patch-package is such a beautiful thing. Thanks again for the PR here I'll merge it but hold for a few days prior to release in order to catch any other changes - you're set via patch-package until then though (it gives you a nice warning when you npm/yarn install after the package it has a patch for changes version so you'll know to clear the patch from source control later)