…rypto object on order data cp-7.72.0 (#27884)

<!--
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**

### Summary
This PR addresses the recurring `Cannot read property "network" of
undefined` error encountered by some users during the offramp flow.

### Context
The issue was identified via multiple user reports and there was already
a [previous
fix](consensys-vertical-apps/va-mmcx-onramp-api#894)
for a similar issue. Users reported that after being redirected back
from the provider's widget to the MetaMask app, the application crashed.
This issue is a blocker for users.

More info can be found on this Slack
[thread](https://consensys.slack.com/archives/C03P2H287N2/p1771581292456779).

### Changes
Added defensive checks to ensure the network object is properly
initialized before access.

### Next actions
Investigation is ongoing with providers to understand why `crypto`
object could be missing in some occasion on order data.

## **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: prevent app crash caused by missing crypto object from
order data

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/TRAM-3393
Ongoing investigation:
https://consensyssoftware.atlassian.net/browse/RAMP-451

## **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**

- [x] 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).
- [x] I've completed the PR template to the best of my ability
- [x] 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]
> **Low Risk**
> Low risk defensive null-checking in `SendTransaction` plus tests; main
behavior change is the screen and send action now no-op/return null when
required crypto/network data is missing, which could hide the CTA for
malformed orders but prevents crashes.
> 
> **Overview**
> Prevents the offramp `SendTransaction` screen from crashing when an
order returns without `cryptoCurrency` (or missing
`cryptoCurrency.network`).
> 
> `transactionAnalyticsPayload` now uses optional chaining for
provider/payment/currency fields, and `handleSend` early-returns if
`chainId` is unavailable; the view also returns `null` when
`cryptoCurrency` is missing.
> 
> Adds/updates tests to cover missing/partial order data (including
analytics assertions and ensuring `addTransaction` is not invoked) and
refreshes snapshots accordingly.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
bdd0b0f. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>