fix: remove max button on Polygon native asset

[SteP-n-s]

Description

Translate Polygon native token address (0x0000000000000000000000000000000000001010) to zero address to prevent logic treating it as an ERC20 token and enabling the Max button.

Changelog

CHANGELOG entry: fix: remove Max button from Polygon native asset

Related issues

Fixes: #22001

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

Normalize Polygon native token (0x…1010) to zero address to detect it as native and conditionally show/hide the Max button; add targeted tests.

• Bridge UI:
  • Normalize Polygon native token address (0x0000000000000000000000000000000000001010) to zeroAddress() before isNativeAddress checks and address formatting in TokenInputArea.
  • Correct Max button visibility for native assets: hidden when gasless swaps disabled, shown when enabled.
• Tests:
  • Add tests verifying Polygon native token is treated as native and Max button visibility toggles with gasless swap flag.
  • Include necessary imports (CHAIN_IDS, POLYGON_NATIVE_TOKEN).

^{Written by Cursor Bugbot for commit 106f8b4. 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
1 Security Hotspot
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud