feat(remote-config): support for custom signals

[russellwheatley]

Description

• Support is for modular only.
• There are discrepancies between native SDKs. iOS will throw if you pass in wrong type (a dictionary is passed in as CustomSignals), I can't see any incorrect type handling on JS (although you ought to get TS warning if incorrect type I think), and android enforces a CustomSignal type which only allows long, double, string and null values. Therefore, we throw exception early if not number, string or null to keep some form of consistency.

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	Feb 6, 2025 3:05pm

[mikehardy]

looks great - really minor nitpicky type comments so attempted to frame them all as committable suggestions to not bog down. All of them are take it or leave it, I'm +1 on merge regardless as they're just opinions not correctness issues

[mikehardy]

of course my text-box code suggestions fail lint 😆