…72.0 (#27881)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
This PR is the first part of Braze integration. It's currently only
creating Braze users based on their profile id, and registering their
FCM/APN tokens to start filling up Braze database with tokens.

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added Braze SDK to enhance push notifications
capabilities

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/GE-107

## **Manual testing steps**

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I've included tests if applicable
- [ ] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new third-party push/engagement SDK and changes native push
handling/initialization on both iOS and Android, which could affect
notification delivery and app startup. Build tooling changes (Kotlin
forcing + patched dependency) also increase risk of platform-specific
build regressions.
> 
> **Overview**
> Introduces Braze as a new mobile dependency and wires it into both
native platforms to start registering push tokens and supporting
Braze-driven notifications.
> 
> On **Android**, adds Braze API key/endpoint injection via Gradle
resources, registers `BrazeFirebaseMessagingService` as the primary FCM
handler with a fallback to the existing RN Firebase service, and
initializes Braze lifecycle callbacks; it also pins Kotlin/serialization
versions and patches `@braze/react-native-sdk` to keep builds compatible
with Kotlin 1.9.
> 
> On **iOS**, adds Braze keys to Info.plists and initializes a shared
`Braze` instance in `AppDelegate` using build-injected credentials,
enabling Braze push automation while preserving the existing permission
flow.
> 
> On the JS side, adds a small `app/core/Braze` layer plus
`useBrazeIdentity` hooked into `useIdentityEffects` to call
`Braze.changeUser(profileId)` on sign-in (skipped in E2E), along with
Jest mocks/tests and new build/CI env vars for Braze secrets (examples,
`build.sh`, workflow, and config verification).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
29b58cd. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->