Ticket 48973 Indexing a ExactIA5Match attribute with a IgnoreIA5Match matching rule triggers a warning
    
    Bug Description:
    	When a index configuration entry (i.e. "cn=<attr>,cn=index,cn=<be_name>,..") contains
    	one or more nsMatchingRule values.
    	A weird warning message can be logged.
    
    	This message should not be a warning, it is more a debug message.
    	Indeed it exists two mechanisms to register MR. So to retrieve an approriate MR
    	the server is first using the old mechanism and if it fails it uses the new one.
    	The old mechanism was going throught the set of indexer function checking one that supports the
    	MR specified in nsMatchingRule.
    	Usually indexer function are not defined and it fallback to new mechanism.
    	In case of several nsMatchingRule, an indexer function is assigned to an MR.
    
    	It is normal that a given MR does not manage syntax it is not designed for.
    	so the message should be DEBUG.
    
    	The message is not that frequent because using nsMatchingRule different from the
    	attribute syntax is not frequent.
    
    	This erronous message came from https://fedorahosted.org/389/ticket/48745
    
    Fix Description:
    	Switch message from warning to debug
    
    https://pagure.io/389-ds-base/issue/48973
    
    Reviewed by: Mark Reynolds and William Brown (thanks !)
    
    Platforms tested: F23
    
    Flag Day: no
    
    Doc impact: no