Improve connection timeout error logging

[jchapma]

Issue Description
When a paged result search is run with a time limit, if the time limit is exceed the server closes the connection with closed IO timeout (nsslapd-ioblocktimeout) - T2. This error message is incorrect as the reason the connection has been closed was because the specified time limit on a paged result search has been exceeded.

Package Version and Platform:

• Package and version: 389-ds-base main branch

Steps to Reproduce

1. Add 1k entries
2. Run a paged result search with a time limit

ldapsearch -H "ldap://localhost:389" -LLL -o ldif-wrap=0 -D "cn=dm" -w password -l 5 -E pr=5 -b "dc=example,dc=com" "(objectclass=inetUser)"  dn

4. Check the access logs for io block timeout error

[14/Feb/2024:11:47:51.245578281 +0100] conn=17 op=-1 fd=65 Disconnect - IO Block Timeout (nsslapd-ioblocktimeout) - T2

Expected results

[15/Feb/2024:16:12:47.014439458 +0000] conn=5 op=-1 fd=125 Disconnect - Paged Search Limit Exceeded - T3

Additional context
Proposed by @tbordaz

[jchapma]

c141e70..8aaf66d 389-ds-base-2.5 -> 389-ds-base-2.5
6a7d13d..9a060d1 389-ds-base-2.4 -> 389-ds-base-2.4
19488f4..3f43fd9 389-ds-base-2.3 -> 389-ds-base-2.3
299d18c..1c69824 389-ds-base-2.2 -> 389-ds-base-2.2
cce70f9..8ec106a 389-ds-base-2.1 -> 389-ds-base-2.1
aea3918..c3ee4c5 389-ds-base-2.0 -> 389-ds-base-2.0
3dfe575..cfb273f 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

[jchapma]

29c79c9..d09c110 389-ds-base-3.0 -> 389-ds-base-3.0