[2.4] Swap out the old ldap_init for the wonderful ldap_initialize

[rdmark]

• Use the more modern ldap_initialize to init LDAP, which enables the use of advanced server URI schemes
• BREAKING The ldap_server options has been replaced by ldap_uri in afpd.conf and has a new syntax
• BREAKING Make the build system check for the ldap_initialize symbol, which requires the system ldap library to supply this symbol
• Update the documentation

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[rdmark]

@dgsga @NJRoadfan I think this is a change that should be made, but it is also a breaking change (afpd.conf syntax, required library), so I'm inclined to hold off on merging this to the stable 2.3 branch.

Rather, I am thinking of planning ahead for a 2.4 feature release in the not too distant future. The mini-roadmap for 2.4 would look something like:

• Meson build system
• WolfSSL to bring the DHX UAM back to life
• This breaking change to LDAP
• Whatever else that comes up in the meantime

Thoughts?

[ghost]

I think it's best to target the meson build system for the 2.4 release as there will no doubt be some snagging to do in the early stages of transition. I also agree with not merging this PR until the regressions are fixed. Making the build system check for the ldap_initialize symbol is a piece of cake with meson, I'll add it to my list of jobs.

Now that the meson implementation is nearly done I'm planning replacement of OpenSSL with WolfSSL for both platforms. It's a simple change that requires the addition of one file. Will discuss this as a separate issue.

[rdmark]

@dgsga I have released 2.3.2 now, and subsequently branched branch-netatalk-2-4 to open up for breaking changes.

Please retarget your Meson PR and other active PRs when it's good timing for you.