Support more field types for ignore_malformed

[felixbarny]

Based on testing

There are a couple of field types that don't support ignore_malformed, yet:

• ip_range
• integer_range
• date_range
• object
• flattened
• nested

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)

[elasticsearchmachine]

Pinging @elastic/es-storage-engine (Team:StorageEngine)

[salvatore-campagna]

As we discussed in in the Logs & Metrics - weekly sync of 27 June 2024 we will not prioritize fixing this for logs since this is already an issue with standard indexing and we do not expect mappings with such field types to use ignore_malformed. That would result in a mapping error no matter the index mode.

[felixbarny]

This is more of a feature request that's orthogonal to LogsDB. It would help that the index-level ignore_malformed setting is more effective in avoiding rejecting a whole document when a single value is malformed. I agree that this isn't required to make LogsDB GA, but it would help in our effort to "accept all logs".