Action Processing Doesn't Work After Cache/DB Reset

[tcm390]

When enabling action processing on the Twitter client, even after removing the cache/DB, the client does not process any actions. Instead, it logs messages like:

Already processed tweet ID: XXXX
Already responded to tweet XXXX, skipping

Even for tweets we haven't interacted with before, the system still considers them as already processed.

This might be due to the initial caching behavior where we store the last 20 tweets and all timelines:
L663
L664

It might be worth reviewing the reasoning behind this initial caching step. If it's unnecessary or causing unintended side effects, we should consider modifying it to ensure tweets are processed correctly after a reset.

[github-actions]

Hello @tcm390! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!