Fix EZP-23037: multiple JOINs in Subtree criterion

JIRA: https://jira.ez.no/browse/EZP-23037

Problem: 
Subtree criterion is used in content search for user roles/permissions in policy and role assignment subtree limitations.
Given enough limitations, this will cause many JOIN clauses on simple content searches.
Depending on conditions, the above can cause severe performance degradation leading to MySQL timeouts (queries not finishing).

Since it seems there is no actual need for multiple joins, and the where conditions can all be done on the same table, this PR replaces the "unique table name join" with a single join clause on the contentobject_tree table, by looking at the existing aliases in `$query`.
@gggeek: not certain if this does impact performance noticeably, given a left/inner join should not expand the result set besides the "normal" object count - the current problem is MySQL does not seem to recognize this with multiple joins.
For example the sort clause already does this:
```
       LEFT JOIN `ezcontentobject_tree` AS `sort_table_0`
              ON `sort_table_0`.`contentobject_id` = `ezcontentobject`.`id`
```
ofcourse, no joins would be better that even one, but otoh performance will be predictable ;)