### Description

I was just looking at some Elasticsearch that had lots of "Improve "reloading search analyzers" logs coming from `MapperService` at the INFO level. In my particular case, it was being emitted because analyzers are reloaded as part of doing a recovery. This log is not really helpful as-is, I think we need to do the following:
 - Switch the level to DEBUG, it's not important enough to warrant an INFO log.
 - Add which index reloaded its search analyzers to the log.

What do you think?
server/src/main/java/org/elasticsearch/index/mapper/MapperService.java
}
    @Override
    public void close() throws IOException {
        indexAnalyzers.close();
    }
    /**
     * @return Whether a field is a metadata field
     * Deserialization of SearchHit objects sent from pre 7.8 nodes and GetResults objects sent from pre 7.3 nodes,
     * uses this method to divide fields into meta and document fields.
     * TODO: remove in v 9.0
     * @deprecated  Use an instance method isMetadataField instead
     */
    @Deprecated
    public static boolean isMetadataFieldStatic(String fieldName) {
        if (IndicesModule.getBuiltInMetadataFields().contains(fieldName)) {
            return true;
        }
        
        return fieldName.equals("_size");
    }
    /**
     * @return Whether a field is a metadata field.
     * this method considers all mapper plugins
     */
    public boolean isMetadataField(String field) {
        return mapperRegistry.getMetadataMapperParsers(indexVersionCreated).containsKey(field);
    }
    /**
     * @return If this field is defined as a multifield of another field
     */