contention info not being resolved

On the table `crdb_internal.transaction_contention_events` the values for `blocking_txn_fingerprint_id` and `waiting_txn_fingerprint_id` are not added on the first insert, but resolved later on.
This resolution should take minutes at most, but there are instances where has been over a day and the values are still set as `0s`.

We use a cache for this mapping resolution, so one possibility is that the cache is getting cleanup (because new data is coming in), before the resolution is done, meaning those values will never get resolved and the table will continue to show values as 0s. This is just one possible interpretation of the cause, it could be a completely different problem causing this behaviour.

Jira issue: CRDB-36911