feat: Add Redesign Permit support; fix: InfoRow padding and alignment

[digiwand]

Description

• Add redesign Permit support
  • Displays appropriate title and subtitle
  • Displays "Spender" if applicable
• Fix InfoRow padding and alignment
  • InfoRow alignItems: 'baseline' was causing inconsistent alignment since each wrapped row has its own relative baseline
• Fix Permit Simulation values not aligning to the right
• Updates DisplayURL test
  • replaces snapshot test
  • fix toBeDefined → toBeTruthy to ensure test checks null case

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3919 (Permit support)
Fixes: #13368 (Permit Simulation value alignment)

Manual testing steps

1. Go to a test dapp
   https://develop.d3bkcslj57l47p.amplifyapp.com/ or https://metamask.github.io/test-dapp/
2. Test various Permit signatures

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.

[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]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 2121a96
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d53e89af-411c-46f8-99a7-8e0ca8518a40

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[jpuri]

most of the translation are label only, this grouping may not be very useful

[digiwand]

I think it's okay for organizational purposes

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE