Dzmitry Lemechko 88871faf60 FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957) ... ## Summary Related to #159582 To better understand the PR, we need to have a look at `esArchiver.load` function and how it handles `mappings.json`: - It processes the file and if it finds saved object index (e.g. `.kibana`), it will delete all SO indexes (.kibana, .kibana_task_manager, .kibana_alerting_cases, etc.) created on Kibana start. Then esArchiver will re-create all indexes according to defined mappings. In order to keep our tests relevant to the latest code changes, it is good to avoid re-creating SO indexes and use "official" ones whenever it is possible. This PR removes/cleans `mappings.json` files where it seems reasonable. I also deleted few not used archives: - es_archiver/saved_objects/ui_counters - es_archiver/saved_objects/usage_counters - security_solution_cypress/es_archives/empty_kibana		2023-06-23 09:04:11 -07:00
..
es_archiver	FTR: delete .kibana mappings from archives to avoid recreating SO indexes (#159957)	2023-06-23 09:04:11 -07:00
kbn_archiver	[Saved Objects] Adds managed to import options (#155677)	2023-04-27 11:17:42 -07:00
import.ndjson	Basic server side import API for saved objects (#32158)	2019-03-08 13:18:36 -05:00
import_managed.ndjson	[Saved Objects] Adds managed to import options (#155677)	2023-04-27 11:17:42 -07:00