EVM plugin wallet provider and transfer action improvements

[nicky-ru]

Relates to:

N/A

Risks

Low.

• The caching mechanism in the wallet provider is isolated and uses a short TTL (5 seconds), which minimizes the impact on operations.
• Changes to the transfer action align with existing types and state management, with no breaking changes expected.

Background

What does this PR do?

This PR introduces improvements and fixes to the EVM plugin:

1. Caching in Wallet Provider: Implements a caching mechanism to store wallet balances for 5 seconds, reducing redundant calls and improving performance.
2. Align Transfer Action: Removes unnecessary template field from the transfer action, aligning it with its intended type and improving clarity.
3. State Update on Transfers: Enhances state updates by populating the state with recent messages for better transfer context.
4. Improved Transfer Template: Refines the transfer template for valid JSON responses and clearer placeholders.

What kind of change is this?

• Features:
  • Added caching to the WalletProvider to reduce redundant operations.
  • Improved transfer template for better JSON response handling.
• Performance:
  • Enhanced state updates in the transfer action for improved context handling.
• Bug Fixes:
  • Aligned transfer action to its intended type, removing unnecessary fields.

Why are we doing this? Any context or related work?

• To improve the performance and maintainability of the EVM plugin that we use in production.
• To ensure the transfer action operates in line with its intended functionality, reducing the risk of errors.

Documentation changes needed?

My changes do not require a change to the project documentation.

Testing

Where should a reviewer start?

1. Review changes in the wallet provider (WalletProvider) for caching logic.
2. Examine the updated transfer action implementation to verify type alignment and state updates.
3. Test the improved transfer template to ensure JSON responses are valid and placeholders function correctly.

Detailed testing steps

1. Run unit tests for the wallet provider to verify caching functionality.
2. Test the transfer action manually by asking an agent for a transfer and checking:
   • Correct state updates.
   • Valid and cached wallet balance in the state.
   • Successful transaction.
3. Verify the cache expiry behavior by observing multiple wallet balance fetches within and outside the 5-second TTL.

Deploy Notes

No specific deploy instructions needed; automated tests and regular deployment process suffice.

Discord username

nikita_zhou

Screenshots

Agent interaction

Link to the tx: https://testnet.iotexscan.io/tx/f946fce5bc127761bd780444bf2d3180bf66fa4944b37e803767e99e76dd0d13

Caching

Linting

Testing

[nicky-ru]

I had to remove the Twitter client and update the plugin-story types locally to successfully build and run the project. Specifically, I updated the story configuration object that was causing build failures and removed the Twitter client, which was preventing the project from starting. However, these fixes are unrelated to the changes in this PR and were not committed, they would require separate attention to address properly

[monilpat]

LGTM - thanks for improving this. Yeah the plugin story should have been address yesterday if you are still having issues after rebasing to latest develop then this is new and will be handled separately.

[monilpat]

LGTM