[Meta] Saved Objects Improvement

[jinmu03]

Add more attributes and metadata to Saved Objects to enable SO related search, versioning, grouping, SO usage statistic analysis.

More requirements include:

• Metadata (Add date created, date modified, other metadata to Saved Objects #9202)
  • SOM UI enhancements ([Saved Objects] Report usage and last used date #125795)
• Tagging ([Meta] Saved Object Tagging #74571)
• Load SO from filesystem (Load saved objects from filesystem #2310)
• Pinned results(requirement is TBD)
• Find should support querying and paging through > 10k documents SavedObjects limit greater than ES max result window #22636
• Read-only assets [Saved Objects] Prevent users from altering managed assets #70461
• Security layer Object Level Security #39259
• Export SO with encrypted attributes Encrypted saved-object attributes cause issues for import/export #82086
• export hidden SO SavedObjects should support importing/exporting even if they're hidden from the API #82027
• Support aggregations on Saved Objects [SAVED_OBJECTS] [AGGS] Step I to add aggregations in the find of saved objects #64002
• SO Migrations should support splitting documents Allow migrations to split documents into new document type #26602
• SO Migrations should support an async pre-migration phase for constructing state Saved object migrations to allow pre-migration state collection #34996
• Dry run migration Dry run migrations #55404
• SO Migrations should support transforming > 100k documents [SIEM] Meta issue for saved object needs for large lists  #64715

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[pgayvallet]

Closing in favor of #101564

[alexfrancoeur]

@pgayvallet @thesmallestduck there are a number of end user capabilities that are listed in this meta issue, but not the new one. I realize these may not be top of mind of our internal developers, but they most certainly are for our end users. Should we create a separate meta issue to track some of these more content management related SO capabilities?

[pgayvallet]

@alexfrancoeur you're right. Reopened it for now, not sure if we want to merge with #101564 which was more shorter-term vision.

[pgayvallet]

Remaining issues are now tracked in more up to date meta issues and boards, so I'll go ahead and close this.

(you won't be able to stop me this time @alexfrancoeur!)