Filtering By Related Tree Models With Non-Unique Names Can Return Unexpected Results

[bryanculver]

          Additional unexpected behavior transforms filtering of parent locations into the parent name and the name of all descendants in the tree (as opposed to the actual descendants in the tree). For example, having the following Location Tree:

Region 1
  Site 1
Region 2
  Site 1
  Site 2

and using the filter {"location": ["Region 2"]}

Would result in location__name__in=["Region 2", "Site 1", "Site 2"]

I would expect this to be location__in=[<LocationRegion1>,<LocationSite1>,<LocationSite2>]

Originally posted by @jmcgill298 in #4207 (comment)

[bryanculver]

Example:

[bryanculver]

Closed via #4330