Ticket 51082 - abort when a empty valueset is freed
    
    Bug Description:
    	A large valueset (more than 10 values) manages a sorted array of values.
            replication purges old values from a valueset (valueset_array_purge). If it purges all the values
            the valueset is freed (slapi_valueset_done).
            A problem is that the counter of values, in the valueset, is still reflecting the initial number
            of values (before the purge). When the valueset is freed (because empty) a safety checking
            detects incoherent values based on the wrong counter.
    
    Fix Description:
    	When all the values have been purge reset the counter before freeing the valueset
    
    https://pagure.io/389-ds-base/issue/51082
    
    Reviewed by: Mark Reynolds
    
    Platforms tested: F30
    
    Flag Day: no
    
    Doc impact: no