chore: Remove redesigned_confirmation from ui_customization property

[dan437]

Description

We no longer need to track if a confirmations is redesign so we can delete this code. Similar thing was done in the extension: MetaMask/metamask-extension#38706

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/6075

Manual testing steps

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

Removes 'redesigned_confirmation' from metrics and conditionally includes only Blockaid-provided ui_customizations; updates related tests and ERC20 tracking event.

• Metrics (signatures)
  • useSignatureMetrics: stop appending redesigned_confirmation; only set ui_customizations when non-empty and pass through Blockaid values unchanged.
  • Refactors analytics params construction accordingly.
• Tests
  • Update useSignatureMetrics.test.ts expectations to remove redesigned_confirmation and reflect conditional ui_customizations.
• ERC20 Tracking
  • useTrackERC20WithoutDecimalInformation: remove ui_customizations from INCOMPLETE_ASSET_DISPLAYED event properties.

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

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeConfirmationsRedesigned
• Risk Level: low
• AI Confidence: 85%

click to see 🤖 AI reasoning details

The changes are purely analytics/metrics-related modifications in the confirmations hooks:

1. useSignatureMetrics.ts: Removes hardcoded 'redesigned_confirmation' from ui_customizations array in analytics params. Now only includes ui_customizations if there are actual customizations from blockaid metrics.

2. useSignatureMetrics.test.ts: Updates test expectations to match the new behavior.

3. useTrackERC20WithoutDecimalInformation.ts: Removes ui_customizations property from ERC20 decimal tracking analytics event.

These changes:

• Only affect what data is sent to analytics events
• Do not change any functional UI behavior
• Do not affect user-facing features
• Are limited to the confirmations flow (signature requests and typed sign simulations)

The risk is low because:

• No functional code paths are changed
• The changes are well-tested (test file updated accordingly)
• Analytics data changes don't affect app behavior

SmokeConfirmationsRedesigned is selected as it covers the confirmation flows where these hooks are used, ensuring the signature and typed sign confirmation flows still work correctly after these analytics changes.

View GitHub Actions results

[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