Fix remaining N+1 queries when users are indexed into elasticsearch

The following discussion from !110915 (merged) should be addressed:

  • @maddievn started a discussion: (+1 comment)

    @dgruzd I still see additional queries for search_membership_ancestry because those need to be calculated on the fly with linear/recursive strategy. Including source takes care of loading the current Namespace but won't be useful for parent/child namespaces, WDYT?

    Screenshot_2023-02-02_at_18.01.03