When we create a view, we check:

1. that the db exists + that the source view or collection also exists in the same db
2. namespace of the view is valid (+ that it doesn't already exist)

In resolveView - which again currently this feature doesn't invoke but hopefully will eventually as part of SERVER-94631 - it checks

1. That the view pipeline doesn't exceed maximum pipeline size
2. that the view depth doesnt exceed maximum depth size

This ticket will add a test that would violate the maximum pipeline size for a view definition and violate the maximum depth size, and then run a search query on it to see if returns an error code.

If an error code is not thrown, that means we're not catching this anywhere. And in that case, we will need to add those checks to findSourceCollectionNamespace