Recently we realized that in specific scenario we could raise a CommandNotSupportedOnView instead of the usual QuaryPlanKilled when restoring a yielded collection acquisition. The specific scenario is the following:

1. we acquire a namespace and there is no collection or view
2. we yield the acquisition
3. a view gets created on that namespace
4. when we attempt to restore the acquisition, we throw CommandNotSupportedOnView

This is different from most of the other scenario, in fact if the collection change during yielding we usually throw QueryPlanKilled (e.g. rename, drop, create collection etc...)

The goal of this ticket is to investigate if raising this error it is actually safe and correctly handled upstream (query engine, router, drivers etc..).