Update the LDAP paging search functionality to resolve potential authentication slowness

When we do a non-paged search, it would seem that LDAP returns a page of results and we just take the first one, and assume that there are no more which causes no delay or slowness in authentication.

When we do paged search we first try to parse the whole results page, thus following referrals even though we just need single result which causes a delay or slowness in authentication. This is not ideal or optimal.

If possible could the respective LDAP class be updated to better handle this referral logic to resolve the potential slowness problems that may be presented and be better optimized.