Proposed commit message

Fix a mapping conflict in Elasticsearch when ingesting documents with the Parameters or ModifiedProperties fields. These fields may sometimes be strings or arrays of strings instead of objects, which conflicts with the existing mapping that defines them as objects. Once a document with an object-type field is ingested, Elasticsearch will reject subsequent documents where the same field is of a different type.

(status=400): {\"type\":\"document_parsing_exception\",\"reason\":\"[1:600] object mapping for [o365audit.Parameters] tried to parse field [Parameters] as object, but found a concrete value\"}, dropping event!

(status=400): {\"type\":\"document_parsing_exception\",\"reason\":\"[1:2] object mapping for [o365audit.ModifiedProperties] tried to parse field [null] as object, but found a concrete value\"}, dropping event!

To resolve this, the PR sets subobjects: false in the mapping for these fields. This change allows Elasticsearch to handle both object and non-object values for these fields without triggering a mapping conflict.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices