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

[lutter]

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.

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.