vlv control may not be logged

[progier389]

Issue Description
vlv_print_access_log that logs the VLV and SORT lines in access log are not called in all failure cases
Typically we see:

[19/Sep/2024:09:01:09.958889789 -0400] conn=174 op=622 SRCH base="ou=certificateRepository,ou=ca,o=ipaca" scope=1 filter="(certStatus=*)" attrs=ALL
[19/Sep/2024:09:01:09.959904830 -0400] conn=174 op=622 RESULT err=1 tag=101 nentries=0 wtime=0.000116293 optime=0.001016967 etime=0.001131581 

and:
[19/Sep/2024:09:01:09.959091978 -0400] - ERR - vlv_build_idl - Can't follow db cursor (err -12797)
So it is clearly a VLV search that is failing (because vlv_build_idl is used) but it is not reported in the access log.

The source code shows that vlv_print_access_log is only called once the response control has been created (and only in some branches of code)
Package Version and Platform:

• Platform: Fedora
• Package and version: main branch (and all older versions)

Steps to Reproduce
Need to be investigated

Expected results
To help troubleshooting easier, vlv_print_access_log should be systematically called before
returning from the search
(if response control is not yet known (i.e: NULL) we should log None in the access VLV lines instead of the vlv control result data

[progier389]

d862f3a..b808a2d main -> main
aaf38ee..e4f6ad3 389-ds-base-3.0 -> 389-ds-base-3.0
8aa9e34..9572c25 389-ds-base-2.5 -> 389-ds-base-2.5