[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.

まず call-cache の実装と call_meta テーブルを特定し、次にキャッシュアクセスのタイムスタンプがどのように記録されるかを追跡します。内部の定期ジョブをどこに配置すべきか、また未使用エントリのしきい値をどのように適用すべきかを判断します。完了の定義は、古く不要な call-cache エントリが定期的に削除され、キャッシュサイズが適切に抑えられていることです。