Revert "[EventLog] change to use Data stream lifecycle instead of ILM"

[pmuellr]

Resolves #164581.

This reverts commit 7e234b1

The commit came from PR #163210

See #164581 for the issue the original PR caused.

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[github-actions]

Documentation preview:

• ✨ Changed pages

[mikecote]

LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 48a835a

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
eventLog	111	116	+5

Unknown metric groups

API count

id	before	after	diff
eventLog	111	116	+5

ESLint disabled line counts

id	before	after	diff
eventLog	3	4	+1

Total ESLint disabled count

id	before	after	diff
eventLog	3	4	+1

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

[pmuellr]

Tested this locally and seems like it works; note you MUST use a DRA build and not a snapshot build, as the snapshot builds somehow enable the dlm feature flag in ES, which enables DLM, but is not enabled by default in 8.10 .0 release.

• download latest 8.10 elasticsearch DRA from here: https://artifacts-staging.elastic.co/dra-info/index.html ; I used commit ab8bf0e9

ensure old behavior can be reproduced, doesn't happen in dev / ci:

• start es via yarn es archive ~/Downloads/elasticsearch-8.10.0-darwin-aarch64.tar.gz --license trial
• check Kibana out at branch 8.10 (without this code)
• start kibana via yarn start
• observe the existing error eventLog initialization operation failed and will be retried: createIndexTemplateIfNotExists in the logs

ensure new code fixes this

• start es the exact same way
• check out this branch of Kibana
• start kibana via yarn start
• observe the event log initializes correctly

I created some rules, checked that the event log is being populated, UX like rule alerts / logs now working again.