[Security Solution][Alert KPI] Fix leading wildcard in KPI visualizations

[christineweng]

Summary

Summary charts and tree map were not handling leading wildcards. This PR updated the query to reflect advanced settings. If leading wildcard is not selected, an error toast should appear.

Related: https://github.com/elastic/kibana/issues/182757

After: when leading wildcard is set to true:

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[kibana-ci]

:broken_heart: Build Failed

• Buildkite Build
• Commit: fecc249b0461bcc1ad82fc160b46fa3bfad5614c
• Interpreting CI Failures

Failed CI Steps

• Jest Tests #5
• Jest Tests #5
• FTR Configs #97
• Serverless Detection Engine - Exceptions - Security Solution Cypress Tests #2

Test Failures

• [job] [logs] FTR Configs #97 / discover/esql discover esql view test should query an index pattern that doesnt translate to a dataview correctly

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	15.1MB	15.1MB	+162.0B

History

• :broken_heart: Build #209885 failed 6e3c0424d57b7a9d7cea420ff3cb378fa00ba2a3

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

cc @christineweng