fix: added energy and bandwidth in transaction confirmation dialog from a dApp

[gabrieledm]

Explanation

This PR fixes Tron dApp transaction confirmations so fee/resource information and balance validation are more accurate.

• Display estimated ENERGY and BANDWIDTH usage in the transaction confirmation even when those resources are covered by available/free/staked resources.
• Show the full estimated energy and bandwidth usage, while charging TRX only for the portion not covered by the user’s available resources.
• Add insufficient-balance detection for dApp transaction confirmations by comparing:
  • native TRX transferred by the transaction
  • estimated TRX fees
  • current native TRX balance
• Disable the confirmation button and show an Insufficient funds banner when the account cannot cover the transaction value plus fees.
• Add getTransactionTrxValue helper to extract native TRX value from:
  • TransferContract.amount
  • TriggerSmartContract.call_value
• Update confirmation context types to include isInsufficientBalance.
• Update/add tests for fee calculation, transaction TRX value extraction, confirmation rendering, and insufficient-balance UI behavior.
  • Followed guidelines to avoid the usage of beforeEach

References

Before

Send

Swap

dApp - Enough funds

dApp - Insufficient funds

After

Send

Swap

dApp - Enough funds

dApp - Insufficient funds

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• [] I've communicated my changes to consumers by updating changelogs for packages I've changed
• [] I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes the transaction signing confirmation gate and fee display for dApp flows; incorrect balance or fee logic could wrongly allow or block signatures.

Overview
Improves dApp transaction confirmations by showing the full estimated energy and bandwidth the transaction will use, even when those resources are covered by staked/free balances. TRX fee math is unchanged—users still pay TRX only for resource shortfalls.

Adds insufficient-funds protection on the confirmation screen: native TRX sent with the tx (TransferContract / TriggerSmartContract call_value) plus estimated TRX fees are compared to the account’s TRX balance. When balance is too low, an Insufficient funds banner appears and Confirm stays disabled.

Supporting updates include getTransactionTrxValue, isInsufficientBalance on confirmation context, fee-calculator test expectations, and changelog/coverage/manifest shasum tweaks.

^{Reviewed by Cursor Bugbot for commit 7201ce3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e88cf2d. Configure here.}

[ulissesferreira]

This is a regression. We want the value to be PT60S as per latest PRs

[gabrieledm]

Sorry about this regression.
Pushing the restored value.