[Security Assistant] Knowledge base conflict fix

[stephmilovic]

Summary

Fixes on merge fail https://buildkite.com/elastic/kibana-on-merge/builds/51840

[kibanamachine]

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/11260140711

[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: - [Security Assistant] V2 Knowledge Base Settings feedback and fixes (#194354) - [Security GenAI] Remove assistantNaturalLanguageESQLTool feature flag and enable by default (#195480)

Manual backport

To create the backport manually run:

node scripts/backport --pr 195659

Questions ?

Please refer to the Backport tool documentation

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 855ac2d

Failed CI Steps

• FTR Configs #75

Test Failures

• [job] [logs] FTR Configs #75 / Machine Learning anomaly detectors POST anomaly_detectors _forecast with spaces should delete forecast for user with permissions

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
securitySolution	20.6MB	20.6MB	+177.0B

[stephmilovic]

FYI I did not backport this because I had to bring the changes from the commit over to a different PR against 8.x in order to avoid problems: e66e06d

So backporting is unnecessary as the code already exists in 8.x

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 195659 locally