fix: use asset ticker else asset.symbol for Price component header text

[nickewansmith]

Description

1. What is the reason for the change?

Ethereum assets on all chains show up on asset details page header as Ethereum(Ethereum)

2. What is the improvement/solution?

Ethereum assets on all chains show up on asset details page header as Ethereum(ETH) as we use asset.ticker but default to asset.symbol used previously

Related issues

Fixes: #12960
Fixes: https://consensyssoftware.atlassian.net/browse/STAKE-915

Manual testing steps

• Click on the native Ethereum asset on any chain to enter the Asset Detail page for that asset
• The asset detail title should be Ethereum(ETH)

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.

[nickewansmith]

https://www.githubstatus.com/incidents/qd96yfgvmcf9

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 353fa1a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/530a86f0-6270-42b5-8875-4c684fae30c3

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b412c09
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/eba34de4-0fa4-41fe-a5e2-86fcfe4257e2

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 9a993a8
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/50f53c98-db89-4787-bf05-62b0b0b7cac3

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 7bc60ef
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/643c1f8a-0975-4cba-b1ce-49a4552b0fef

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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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