@GrahamcOfBorg test ldap

I guess the ldap test wasn't a good choice because apparently it is broken in master right now 😞
I tested this change and it eliminates error messages on nslcd.service restart.

Uff, it used to work…

Did you verify things still work with a local setup? I'd rather see this being tested somehow, if we can't get the tests to work right now…

I deployed this change to a nixops machine and was able to access the machine via ssh with a password. I ran journalctl -f -u nslcd.service both while I deployed and while I logged in - there were no errors.

I'll run some more tests, including running a command via sudo as well as a local login and then report back 👍

With this change I have confirmed that for an account authenticated via ldap:

• remote ssh logins work with a password
• remote ssh logins work with a key
• local logins work with a password
• sudo rules work
• getent passwd username yields the expected results
• getent.ldap passwd username yields the expected results
• there are no more errors in journalctl

After reading through source code to better understand where these errors might be coming from, combined with the mentioned testing I believe this PR is ready for a merge.

Alright. Thanks :-)