Ticket 47350 - Allow search to look up 'in memory RUV'
    
    Bug Description:
    
    	On a running instance and for a given replica the RUV is an in memory data structure.
    	This data structure is writen to disk at each update and there it is named database RUV.
    	With ticket https://fedorahosted.org/389/ticket/564, the update of the database RUV would be done
    	asynchronously. The consequence is that the database RUV would be late compare to the current
    	update status.
    	It is important for monitoring reason to look up the current update status and so to be able to
    	read the in memory RUV
    
    Fix Description:
    
    	The fix consists to return the in memory RUV if attributes "nsds50ruv" and/or "nsruvReplicaLastModified" are
    	requested when reading the entry (replica_config_search):
    		cn=replica,cn=\"<suffix>\",cn=mapping tree,cn=config
    
    	In addition to provide backward compatibility, if the database ruv is lookup
    	(i.e. nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,<suffix>), it actually returns the in memory ruv
    	(i.e. cn=replica,cn=\"<suffix>\",cn=mapping tree,cn=config). This is achieved with a registered MMR preop callback
    	(multimaster_preop_init), that is called when send the result entry (SLAPI_PLUGIN_PRE_ENTRY_FN).
    
    https://fedorahosted.org/389/ticket/47350
    
    Reviewed by: Rich Meggison, Noriko Hosoi
    
    Platforms tested: F17
    
    Flag Day: no
    
    Doc impact: no