[Feature] Implement a way to clean up the call cache

Description

Currently, we only ever write to the call cache, but never remove unneeded entries from it. The call cache can grow quite large, and removing unneeded entries from that will help keep its size in check.

We already have a table call_meta that tracks how long ago a cache entry was last accessed. We should add an internal job that periodically removes entries that haven't been used in a while.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out

• Tick this box if you plan on implementing this feature yourself.
• I have searched the issue tracker to make sure this issue is not a duplicate.

Inizia individuando l’implementazione di call-cache e la tabella call_meta, quindi segui come vengono registrati i timestamp degli accessi alla cache. Determina dove debba essere collocato un job periodico interno e come debba essere applicata una soglia per le voci non utilizzate. Il lavoro è completato quando le voci di call-cache obsolete e non necessarie vengono rimosse periodicamente e le dimensioni della cache restano sotto controllo.