feat(app-check): Replay Protection

[apetta]

Description

This PR adds the Replay Protection feature for App Check, where it provides a consumable token for single-use server calls.

Related issues

#7394

Release Summary

• Introduces Replay Protection feature for App Check
• getLimitedUseToken Provides single-use tokens for enhanced security on the server.

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

Tested in a private repo with the emulator.

---

[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 27, 2023 8:20pm
react-native-firebase-next	❌ Failed (Inspect)			Nov 27, 2023 8:20pm

[CLAassistant]

All committers have signed the CLA.

[mikehardy]

Nice!
I think there should be entries in the index.d.ts files so that they are available in typescript?
Also, I think it should be possible to add an entry for this in the e2e test suite for app-check, that way we can see in CI that the methods really are working + not crashing (also, they will help you determine locally that they are working before pushing to the PR branch - best practice is to add an e2e test and put .only on it so when you run the suite locally it is super fast to run it + iterate on code changes

[apetta]

Thanks!

I remember I couldn't get the project installed locally last time I tried, so I had to skip the tests. Will try and look at this again soon

[mikehardy]

When I took this one and attempted to add tests to it, it hung on iOS - need to investigate why but I suspect it has something to do with not being able to proxy to the currently configured provider from our custom provider, and calling the API directly on the FIRAppCheck.

It appears this new API isn't implemented on the Provider interfaces unlike getToken, for some reason, and I've got an API shape question out upstream to see if I can understand it better firebase/firebase-ios-sdk#11284 (comment)

[mikehardy]

worked through my iOS question with more investigation, made iOS implementation proxy to current delegate
added e2e test and it works locally now for iOS and android (which delegates to current provider w/out proxy)
added typescript API definition,
formatted,
rebased to main,
re-pushed

should be good to go assuming CI goes ✅

[apetta]

Thank you so much!!

[mikehardy]

I pushed those changes at the same time github suffered an outage. Just closing / reopening to kick off the CI jobs that should have run