We've written the run_aggregate path to be mostly "unaware" if it's running over a resolved view or a normal collection. We should move view resolution and namespace resolution to be internal to AggregationPlan to cement that separation so that developers in run_aggregate generally don't need to worry about that distinction.