Fix type issue resulting from #193415 & #193791

[delanni]

Summary

As the title says. Two competing changes made it in to main (#193415 & #193791), causing a type issue: https://buildkite.com/elastic/kibana-on-merge/builds/50786#019228ae-4487-45c6-867a-ba0590b1266d

cc: @davismcphee @stratoula

[stratoula]

Thanx Alex for the PR! @davismcphee know the changes in both PRs better than me but the change makes sense to me!

[jughosta]

Let's merge, thanks! 👍

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 43a4501

Failed CI Steps

• Jest Integration Tests #3

Test Failures

• [job] [logs] Jest Integration Tests #3 / when rolling back to an older version kibana should detect that a later version alias exists, and abort

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
cloudSecurityPosture	497.7KB	497.7KB	+18.0B
discover	813.8KB	813.9KB	+18.0B
esqlDataGrid	154.0KB	154.0KB	+18.0B
securitySolution	20.4MB	20.4MB	+90.0B
slo	855.1KB	855.1KB	+18.0B
total			+162.0B

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

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts You might need to backport the following PRs to 8.x: - [[ES

Manual backport

To create the backport manually run:

node scripts/backport --pr 193970

Questions ?

Please refer to the Backport tool documentation

[delanni]

Backport not needed, as types are fixed in: #193962

[kertal]

@delanni thx for cleaning/closing all those test failures