Performance issue when amalgamating groups for a findAllGroupRelationships call

For a findAllGroupRelationships call, if you have multiple directories with the same group across directories OR if you have a group with the same name that appears multiple times in your group subtree scope:

• the first instance of the group will correctly have the group members (subgroups) amalgamated to the results (correct behaviour)
• any subsequent instance of the group will have the principal members amalgamated to the results (incorrect behaviour)

For very large user bases with very large duplicated groups, this can manifest itself as a significant performance issue.

The fix will involve patching the amalgamation code in ApplicationServiceGeneric.searchGroups() on the 1.6 branch. This issue is not present on the 2.0 branch as searching has been completely revamped.