Make query yielding aware of AutoGetCollection at high level

With lock free reads, restoring locks and state after query yielding may cause Collection pointers held by AutoGetCollection and other helpers at a high level to be invalid and dangle.

There might have come a MODE_X writer that installed a new Collection instance into the Collection catalog during the window where yield had the locks released.

We need to add a way to pass any AutoGetCollection instances to the query plan executor so they can be notified to refresh their state when we restore after yield.