### 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
);
    public static final Setting<Long> INDEX_MAPPING_FIELD_NAME_LENGTH_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.field_name_length.limit",
        Long.MAX_VALUE,
        1L,
        Property.Dynamic,
        Property.IndexScope
    );
    public static final Setting<Long> INDEX_MAPPING_DIMENSION_FIELDS_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.dimension_fields.limit",
        21,
        0,
        Property.Dynamic,
        Property.IndexScope
    );
    private final IndexAnalyzers indexAnalyzers;
    private final MappingParser mappingParser;
    private final DocumentParser documentParser;
    private final IndexVersion indexVersionCreated;
    private final MapperRegistry mapperRegistry;
    private final Supplier<MappingParserContext> mappingParserContextSupplier;
    private volatile DocumentMapper mapper;
    public MapperService(
        ClusterService clusterService,
        IndexSettings indexSettings,
        IndexAnalyzers indexAnalyzers,
        XContentParserConfiguration parserConfiguration,
        SimilarityService similarityService,
        MapperRegistry mapperRegistry,
        Supplier<SearchExecutionContext> searchExecutionContextSupplier,