fix: stop showing incoming transactions

[ulissesferreira]

Explanation

Incoming/received transactions pose an address poisoning risk. Attackers send small token amounts to a user's address so that their (attacker's) address -- often visually similar to a legitimate one -- appears in the user's transaction history. Users may then accidentally copy and reuse the attacker's address for future transfers.

This PR stops mapping all incoming (receive) transactions in TransactionMapper. Only outbound transactions (send, swap, stake deposit, stake withdraw) and unknown/approval types are now mapped and returned to the client.

What changed

TransactionsMapper.ts -- receive filtering is centralized at two aggregation boundaries instead of scattered across individual mappers:

1. mapTransaction -- the switch now assigns to a mapped variable instead of returning directly, and a single post-dispatch check filters out any result with type === TransactionType.Receive. This covers all raw transaction types (native TRX, TRC10, TRC20, staking) in one place.
2. mapTransactions -- the TRC20-only loop (for transactions not covered by raw data) has a single mappedTx.type !== TransactionType.Receive guard.

Individual mappers (#mapTransferContract, #mapTransferAssetContract, #mapTriggerSmartContract, #mapTrc20OnlyTransaction) remain unchanged in their mapping logic -- they still compute the type via #computeTransactionType, but no longer contain duplicate receive checks.

Staking (StakeDeposit / StakeWithdraw) and swap transactions are not affected -- they use dedicated types that are never Receive.

TransactionsMapper.test.ts:

• Added explicit test: native TRX receive returns null
• Updated 5 existing tests that previously asserted TransactionType.Receive to now assert null / empty results
• Updated mapTransactions batch tests to reflect reduced counts (incoming transactions excluded)
• All 31 tests pass (608 total across the full suite)

snap.manifest.json:

• shasum updated to match the new build output

jest.config.js:

• Coverage thresholds adjusted to reflect the refactored branch/line/statement coverage

CHANGELOG.md:

• Added entry under [Unreleased] > Changed

References

• Fixes NEB-723

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