fix: Add PPOM validation for deeplink requests

[OGPoyraz]

Description

This PR aims to add PPOM validation requests for deeplinks.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/2370
Fixes: #17358

Manual testing steps

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

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). 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.

---

Note

Integrates PPOM validation into deeplink transfer/approve flows, generating a securityAlertId and passing it to addTransaction, with refactors and tests.

• Deeplink handling (app/components/Views/confirmations/utils/deeplink.ts):
  • Add validateWithPPOM to build a PPOM request (with uuid-based securityAlertId) and call ppomUtil.validateRequest.
  • Pass returned securityAlertResponse to addTransaction for both native and ERC20 transfers.
  • Refactor tx construction to derive txParams and transactionType; downgrade duplicate-request log from error to log.
• Approve flow (app/core/DeeplinkManager/TransactionManager/approveTransaction.ts):
  • Compute chainId/networkClientId, call validateWithPPOM, and include securityAlertResponse in addTransaction.
• Tests:
  • Extend deeplink and approve tests to mock PPOM and UUID, assert PPOM validation payload, securityAlertResponse, and networkClientId wiring.

^{Written by Cursor Bugbot for commit daa4941. This will update automatically on new commits. Configure here.}

[OGPoyraz]

This is causing false positives in the Sentry logs - hence we are decreasing it to log instead of error.

See comment here: #17358 (comment)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud