### 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 String TYPE_FIELD_NAME = "_type";
    public static final Setting<Long> INDEX_MAPPING_NESTED_FIELDS_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.nested_fields.limit",
        50L,
        0,
        Property.Dynamic,
        Property.IndexScope
    );
    
    public static final Setting<Long> INDEX_MAPPING_NESTED_DOCS_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.nested_objects.limit",
        10000L,
        0,
        Property.Dynamic,
        Property.IndexScope
    );
    public static final Setting<Long> INDEX_MAPPING_TOTAL_FIELDS_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.total_fields.limit",
        1000L,
        0,
        Property.Dynamic,
        Property.IndexScope,
        Property.ServerlessPublic
    );
    public static final Setting<Long> INDEX_MAPPING_DEPTH_LIMIT_SETTING = Setting.longSetting(
        "index.mapping.depth.limit",
        20L,
        1,
        Property.Dynamic,
        Property.IndexScope