Version control on index mapping

[angorayc]

Suggested requests

1. Adding updated version / time will be helpful for data quality dashboard to highlight the changes of an mapping.
2. What we can also do is to provide an option to allow user save their historical mappings, so we can render a mapping diff on the UI side and point out exactly which part of their mapping is changed.

There are two features that will be beneficial if we have "version control" to users mapping:

1. This requirement is due to an issue that users mapping was changed unintentionally. With the "updated version/time" of the mapping, users can be indicated that their mapping was changed: https://github.com/elastic/kibana/issues/179827
2. Security Solution data quality dashboard is planning to save the users checking result after each time they run the check. It would be helpful if users could see which version of the mapping they were checking : https://github.com/elastic/security-team/issues/8527

Here is the current response of the get mapping api:

I created an index, it show me a created version

I updated the index mapping, it wouldn't show me any information that indicates the mapping has changed expect the mapping itself. I'd hope that we can add a updated version and time to the get index api

It'd be very help for user if we have the version updated according to the mapping changes, as from the SDH above, our user doesn't know which version of mappings they are checking and if it has been changed since created. So from the historical record of the data quality check result, they'll be able to know exactly which version of their mapping has problem.

Originally posted by @angorayc in https://github.com/elastic/kibana/issues/179827#issuecomment-2076950596

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)