feat: Add bulk token scanning and introduce shared cache manager #6617

[AugmentedMode]

Explanation

This PR extends the PhishingController to support bulk token screening with caching, similar to the existing URL scanning functionality. This PR also replaces the urlScanCache with a reusable cacheManager class that is shared between both urlScanCache and now tokenScanCache

Changes introduced

• Added a new bulkScanTokens method that can screen up to 100 tokens per batch
• Implemented a new cacheManager class that handles caching logic with a 15-minute TTL.
  • Replaced urlScanCache with cacheManager.
  • Introduced tokenScanCache using the same cacheManager for consistency and reuse.
• Defined cache key format as ${chainId}:${tokenAddress} for token scans.
• Registered bulkScanTokens as a controller action under PhishingControllerBulkScanTokensAction.
• Exported new types for extension consumption and exposed the scanning functionality via the messenger.

Screenshot showcasing the tokenScanCache is implemented as expected

This is grabbed via the extension console using await stateHooks.getPersistedState() after triggering a swap in uniswap. You will notice i was doing a swap for USDC which is the only token address stored in the cache.

References

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes