Fix find LdapTemplate, specifying return attributes.

[orlandosso]

LdapQuery allows the user to define ToReturn attributes, but does not respect the attributes defined.

String [] atributtes = new String [] {"cn", "name", "email"};

var queryLdap = LdapQueryBuilder.query ()
        .attributes (attributtes)
        .base ("ou = company, o = department")
        . where ("cn"). is ("123456");

var user = ldapTemplate.findOne(queryLdap, UserEntity.class);

The attributes are just ignored, and overwritten by following code.

String[] attributes = this.odm.manageClass(clazz);
searchControls.setReturningAttributes(attributes);

The correction involves verifying that the attributes for return have been informed.

if (isNotCustomReturningAttributes(searchControls)) {
            String[] attributes = this.odm.manageClass(clazz);
            searchControls.setReturningAttributes(attributes);
}

[rwinch]

Thanks for the PR. Can you please add test(s) to the PR?

[rwinch]

Please add tests

[jzheaux]

Hi, @orlandosso, thanks for your contribute.

Are you able to address Rob's feedback? I can help sort things out, if not. If I haven't heard from you in a week or so, I'll apply the described changes myself.

[pivotal-cla]

@orlandosso Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[jzheaux]

This is now merged into 2.4.x with df40b39 and a polish of 255bfaa.

Note that the polish changes the behavior so that returning attributes are only populated if the value is initially null instead of if it is null or empty.

This is also now merged into main.