### Elasticsearch Version

8.11+

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

any

### Problem Description

While indexing documents with dynamically added fields, if multiple of those fields are objects are are deeper than 3-5 objects, performance is degraded significantly.

This bug was introduced in: https://github.com/elastic/elasticsearch/pull/90674

### Steps to Reproduce

I built a micro-benchmark to replicate this particular bug. 

But, any dynamic object parsing will cause this.

To mitigate the issue, statically mapped fields for objects is required. 

### Logs (if relevant)

Attached are two JFR files indicating the difference between when the bug was introduce vs. not.
[Archive 2.zip](https://github.com/elastic/elasticsearch/files/13569248/Archive.2.zip)

server/src/main/java/org/elasticsearch/index/mapper/DocumentParserContext.java
return idMapper.documentDescription(this);
    }
    public Mapper getMapper(String name) {
        return parent.getMapper(name);
    }
    public ObjectMapper.Dynamic dynamic() {
        return dynamic;
    }
    public void markFieldAsAppliedFromTemplate(String fieldName) {
        fieldsAppliedFromTemplates.add(fieldName);
    }
    public boolean isFieldAppliedFromTemplate(String name) {
        return fieldsAppliedFromTemplates.contains(name);
    }
    public void markFieldAsCopyTo(String fieldName) {
        copyToFields.add(fieldName);
    }
    public boolean isCopyToField(String name) {
        return copyToFields.contains(name);
    }
    /**
     * Add a new mapper dynamically created while parsing.
     */
    public final void addDynamicMapper(String fullName, Mapper.Builder builder) {
        
        if (builder instanceof ObjectMapper.Builder) {
            MappingLookup.checkObjectDepthLimit(indexSettings().getMappingDepthLimit(), fullName);
        }