Update all involved allocators before performing queries over links

[tgoyne]

This is an attempt at a more general solution to the same problem as f045da0. There are several places where queries are using the allocator from one Table while accessing another Table. Rather than attempting to validate that all of them are correct, instead update each Table's WrappedAllocator before running the query so that it doesn't matter which one is used.

AFAICT this is a perfectly safe thing to do, but it's possible I've misunderstood something. It appears that not updating each WrappedAllocator immediately is a perf optimization and not something required for correctness (or maybe there just isn't an easy way to do it?), and this should be thread-safe for frozen transactions as it's assigning to an atomic variable with proper sequencing.

[jedelbo]

I created #4417 as an alternative solution. I will let @finnschiermer rule.

[finnschiermer]

I prefer #4417 since it maintains the relation between Table and it's allocator. I'm afraid deviating from this opens up for wrong assumptions and new errors down the line if we add functionality to the WrappedAllocator - or access the version counters in a new setting.