When using composite field selectors the output results in multiple AND nodes referring to the same selector

[jeme]

When using composite field selectors the output results in multiple AndResult nodes referring to the same selector

This results in a strange form of duplication in descriptors, e.g:

    id & username & email
    is required - actual value was: NULL
    AND
    id & username & email
    is required - actual value was: NULL
    AND
    id & username & email
    is required - actual value was: NULL

This is because of the way we put results together in the BasicRule and EmbededValidatorRule where we use a AndResult for all selected entities. (Which makes sense for e.g. array selectors)...

We could solve this by providing special result classes for the two rules which just inherits from AndResult (Same feature set but allows the descriptors to react differently if required or default back to AndResults).

There could also be other ways to solve this.