This issue is a temporary workaround for elastic/package-spec#441 and #1017, discard it if the other issues are prioritized first.

For packages importing fields from ECS, import a hard-coded list of fields that are commonly used and can be a source of conflicts if they don't have any mapping.

Update: instead of adding specific fields, include dynamic mappings as described in #1018 (comment). We have to try how to add the dynamic mappings:

• If we add these dynamic mappings using fields.yml, this would only be supported by versions of kibana implementing [Fleet] Support dynamic_template mappings from object field kibana#137772 (>= 8.4.0).
• If we add the dynamic mappings in the manifest, we will cover more versions of the stack, but we have to be careful of merging correctly with other existing configurations, and it may be difficult to check for documented fields in tests.
  • Add support for elasticsearch.index_template key in packages and a new flag to opt in Add elasticsearch mappings definitions into input packages and a key to opt-in to import common definitions package-spec#455
  • Import templates in elastic-package Add common dynamic mappings and properties from ECS automatically #1073
  • Add imported templates as definitions to be used in tests Add ECS mappings during test runner executions #1090

Fields imported this way should be imported in a new well-known fields file that can be discarded later by Fleet if elastic/kibana#144048 is implemented. For example they could be included in a file called fields/imported_elastic_package.yml.

Fixes elastic/integrations#4236.