fix(tron): correct unstaking withdrawal period from 3 to 14 days

[ulissesferreira]

Description

The trx_locked_for_minimum_time localization key was displaying ~3 days across all supported languages as the estimated Tron unstaking duration. The actual withdrawal period is 14 days. This fix updates the value in all 15 language files (de, el, en, es, fr, hi, id, ja, ko, pt, ru, tl, tr, vi, zh).

Note: the sibling key trx_released_in_minimum_time already had the correct value of ~14 days.

Changelog

CHANGELOG entry: Fixed incorrect Tron unstaking withdrawal period display from 3 days to the correct 14 days.

Related issues

Fixes: NEB-720

Manual testing steps

```gherkin
Feature: Tron unstaking withdrawal period

Scenario: user views Tron staking information
Given the user has TRX staked
When user navigates to the staking details screen
Then the TRX locked for minimum time should display ~14 days
```

Screenshots/Recordings

Before

~3 days shown for TRX locked for minimum time

After

~14 days shown for TRX locked for minimum time

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

Low Risk
Low risk localization-only change; it only updates displayed text for the Tron staking lock period with no logic or data-flow changes.

Overview
Corrects the Tron staking/unstaking informational string trx_locked_for_minimum_time from ~3 days to ~14 days across all translated locale JSON files, aligning the displayed minimum lock period with the existing 14-day release/unstaking messaging.

^{Written by Cursor Bugbot for commit 4ea43e7. 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: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 97%

click to see 🤖 AI reasoning details

E2E Test Selection:
All 15 changed files are locale/language JSON files. Each file contains exactly one change: updating the trx_locked_for_minimum_time string from "~3 days" (in each respective language) to "~14 days". This is a pure copy/text correction for the TRX staking lock period display string across all 15 supported languages (de, el, en, es, fr, hi, id, ja, ko, pt, ru, tl, tr, vi, zh). No application code, components, controllers, navigation, or shared infrastructure was modified. No E2E tests specifically validate this TRX staking lock period string value. The change does not affect any shared components (TabBar, modals, confirmations) that could break existing tests. No performance impact from locale string changes.

Performance Test Selection:
Pure locale string update with no code changes. No performance impact whatsoever from changing a display string value in JSON locale files.

View GitHub Actions results

[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 SonarQube Cloud

[ulissesferreira]

Closing this PR because we are actually displaying everything correctly. The problem we saw was simply a user that did not understand what the locked for terminology meant. We are telling users that they must stay staked for at least a minimum of 3 days before they trigger their unstake, not that they can unstake right away after 3 days