[Alerting] Add alert.updatedAt field to represent date of last user edit

[ymao1]

Resolves #83578

Summary

Re-do of this PR: #83578

Original Summary

Adds updatedAt field to the alert saved object that is updated when a user acts on an alert (updates the name or parameters or mutes/unmutes or enable/disables).

The original PR did not touch any code that triggered the Security Solutions cypress test suite so those tests were not run on the PR. Once merged into master, the cypress tests failed because they were loading alert saved objects from the esarchiver without the updatedAt field (something which would be taken care of by the migration)

This is the commit that updates the esarchive data for the security solutions tests (and unskips the test suites) c150217

This is the output of the cypress tests on this branch https://github.com/elastic/kibana/runs/1425449442

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: c150217

Metrics [docs]

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/development-plugin-saved-objects.html#_mappings

id	before	after	diff
alert	30	31	+1

History

• 💚 Build #88882 succeeded 424af92

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[dhurley14]

LGTM. Thanks for the cypress fixes!

[pmuellr]

So the only change from the original PR is the additional security cypress test stuff?

Does that mean the original PR was reverted? I would have expected a reference to the reverted commit somehow in that PR, if so. But didn't see one.

The original PR did not touch any code that triggered the Security Solutions cypress test suite so those tests were not run on the PR

Seems like we need to get that fixed, or it'll happen again the next time we update the alert SO mappings ... fixed as in "those tests need to run if anything in alerting changes (and maybe actions and task manager and event log ...)". Not sure who we talk to about that tho ...

[ymao1]

@pmuellr Yes, I reverted the original PR.

Revert commit on master here: 6a2c415
Revert commit on 7.x here: 8a8e24b

I have talked to @dhurley14 and he believes there is an issue open already for updating the paths that will trigger the Security Solutions Cypress tests. If he's unable to find it, then I will open an issue for it.

[pmuellr]

LGTM

[ymao1]

Issue created here: #83851