[Security Solution] [AI Assistant] Introducing security labs content as an integration

[KDKHD]

Proposed commit message

Introducing a new integration for the security labs content from https://www.elastic.co/security-labs. The content from security-labs is used to improve the capabilities of the security AI assistant by giving the assistant context on security threats.

Users do not need to install this integration through the integrations page in Kibana. Rather, the integration will be installed when a user sets up the Security AI assistant knowledge base under http://localhost:5601/app/management/kibana/securityAiAssistantManagement?tab=knowledge_base.

Why

Currently, the security labs content is included in the Kibana repository. There are several problems with the current approach that this integration will solve:

1. As the security labs content contains information about malware, it is triggering antivirus software, preventing users from upgrading Kibana (Kibana Knowledge Base Files being detected as Malware after update to 8.16 kibana#202114). Moving the content to an integration and removing the Security Labs content from the Kibana build, will ensure that anti virus software does not prevent users from upgrading Kibana.
2. In addition to the raw content, we would like to include the embeddings for that content in the integration. This way we do not need to generate the embeddings on the user's cluster. In the future, embeddings for the security labs' content can be shipped through this integration. The embeddings are not included in the integration yet, this will be added in the future.

Requires elastic/package-spec#900

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 38f5b08

Failed CI Steps

• Check integrations security_labs_content

History

• 💔 Build #26249 failed f861008
• 💔 Build #26240 failed aa7233f
• 💔 Build #26239 failed 7b66619
• 💔 Build #26232 failed 2401d91

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!