Docs: Document behavior and recommend approach for dealing with pagination across a query whose view is changing

Need some documentation to describe how our software works, and how developers should work with it regarding paginating over a view that is changing.

For example, a customer is trying to iterate over 100M items (in 50 item "pages") and delete the data. However, since the delete is eventually consistent and the view update is going on in the background, he is not able to see all of the items because the paging skips over it.

The same situation would apply when paginating over a view that has items being added to it.

This is really just about describing this as a higher-level use case and what our recommendations for dealing with it would be.