Ticket 47527 - Allow referential integrity suffixes to be configurable
    
    Bug Description:  Request to apply referential integrity operations
    			to specific subtrees only
    
    Fix Description:  The fix adds two configuration parameters to the
    	referential integrity plugins:
    	nsslapd-pluginContainerScope: <dn>
    	nsslapd-pluginEntryScope: <dn>
    
    	The logic implemented is:
    		Only entries in the nsslapd-pluginContainerScope will
    		be searched for references to be handled
    		Only for entries for which nsslapd-pluginEntryScope is
    		a suffix will be considered for referential integrity
    		processing. This results in a different bahaviour for
    		modrdn operations in some scenarios:
    		if an entry is renamed and the new superior is not
    		below nsslapd-pluginEntryScope then the reference to the
    		original dn is removed, like a delete.
    		For consistency also a modrdn, which moves an entry
    		into scope will be considered: if the old rdn is already
    		referenced in an entry inside the containerscope its reference
    		will be updated to the newdn
    
    https://fedorahosted.org/389/ticket/47527
    
    Reviewed by:  Mark,Rich -Thanks