fix: Snap Address component UI/UX (Snaps custom UI)

[david0xd]

Description

Because of concerns around Snap custom UI address component not working as intended with Pet Names, decision was made to disable it's interactive UX and display shortened hexadecimal address instead of showing Pet name.

Changes on this PR will make Address component to ignore clicks and triggering the modal for nicknames.

Changes are applied only to Snaps related flows where Snaps components (custom UI) are used.

Related issues

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

Manual testing steps

1. Try using a Snap with Custom UI which has Address component.
2. Try clicking on the Address component.
3. Nothing should happen when Address component is clicked.
4. Make sure that address component is not displaying nicknames (only short hex address is required).

Screenshots/Recordings

Before

After

Customized Interactive UI Snap for the test case, just for reference:

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.97%. Comparing base (97246c5) to head (de76f97).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #26477   +/-   ##
========================================
  Coverage    69.96%   69.97%           
========================================
  Files         1405     1405           
  Lines        48996    48998    +2     
  Branches     13697    13699    +2     
========================================
+ Hits         34280    34282    +2     
  Misses       14716    14716           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[metamaskbot]

Builds ready [23331d5]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (73 ± 10 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	78	164	106	22	11
		domContentLoaded	11	76	29	14	7
		load	48	120	73	22	10
		domInteractive	11	76	29	14	7

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 11 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[metamaskbot]

Builds ready [de76f97]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5
  • common: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (84 ± 9 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	75	167	113	24	12
		domContentLoaded	54	114	80	18	8
		load	60	118	84	18	9
		domInteractive	17	54	29	10	5

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 164 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[jpuri]

Change look good, will be nicer to have unit test coverage also.