[LDAP-39] Correct usage of ALL special class to ANY

[Sylinsic]

Following LDAP-37 and further configuration of a syncope instance, it was realised that when the “any object classes” capability was used for multiple object classes, the configuration values weren’t being utilised for all any objects.

It was then realised, that these would apply to the ALL special class, however, that then prevented search capabilities.

This fix is to make use of the ANY special class, instead of ALL, which can then be used in a resource mapping to pull the object classes from the resource configuration.

[ilgrosso]

@Sylinsic as you can see, the build is failing:

[INFO] Results:
[INFO] 
Error:  Failures: 
Error:    LdapSearchTests.anyObjectSearchFilter:564 expected: not <null>
Error:  Errors: 
Error:    LdapCreateTests.createArbitraryWhenUidNotDefault:190->doCreateArbitrary:199 » Connector
Error:    LdapSearchTests.configurableAnyObjectScope » UnknownUid Object with Uid 'Attri...
[INFO] 
Error:  Tests run: 181, Failures: 1, Errors: 2, Skipped: 0

[Sylinsic]

Serves me right for adding an extra line in when transferring from my other device!

[ilgrosso]

Thank you @Sylinsic !