…ure Flag API Integration Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts - Stateful Observability feature flag testing - Deployment-agnostic API integration tests SyntheticsCustomStatusRule "after all" hook in "SyntheticsCustomStatusRule" (elastic#225090)

## Summary

It fixes elastic#224778
✅ Falky test runner
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441
### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit e140d22)

…ure Flag API Integration Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts - Stateful Observability feature flag testing - Deployment-agnostic API integration tests SyntheticsCustomStatusRule "after all" hook in "SyntheticsCustomStatusRule" (elastic#225090)

## Summary

It fixes elastic#224778
✅ Falky test runner
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441
### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

(cherry picked from commit e140d22)

…ic Feature Flag API Integration Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts - Stateful Observability feature flag testing - Deployment-agnostic API integration tests SyntheticsCustomStatusRule "after all" hook in "SyntheticsCustomStatusRule" (#225090) (#225266)

# Backport

This will backport the following commits from `main` to `8.19`:
- [FIX - Failing test: Stateful Observability - Deployment-agnostic
Feature Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule "after all" hook in
"SyntheticsCustomStatusRule"
(#225090)](#225090)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Faisal
Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2025-06-25T11:15:24Z","message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-management","v9.1.0","v8.19.0","author:obs-ux-management"],"title":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\"","number":225090,"url":"https://github.com/elastic/kibana/pull/225090","mergeCommit":{"message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225090","number":225090,"mergeCommit":{"message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co>

…c Feature Flag API Integration Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts - Stateful Observability feature flag testing - Deployment-agnostic API integration tests SyntheticsCustomStatusRule "after all" hook in "SyntheticsCustomStatusRule" (#225090) (#225267)

# Backport

This will backport the following commits from `main` to `9.0`:
- [FIX - Failing test: Stateful Observability - Deployment-agnostic
Feature Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule "after all" hook in
"SyntheticsCustomStatusRule"
(#225090)](#225090)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Faisal
Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2025-06-25T11:15:24Z","message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","Team:obs-ux-management","v9.1.0","v8.19.0","author:obs-ux-management"],"title":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\"","number":225090,"url":"https://github.com/elastic/kibana/pull/225090","mergeCommit":{"message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225090","number":225090,"mergeCommit":{"message":"FIX
- Failing test: Stateful Observability - Deployment-agnostic Feature
Flag API Integration
Tests.x-pack/test/api_integration/deployment_agnostic/apis/observability/alerting/synthetics/custom_status_rule·ts
- Stateful Observability feature flag testing - Deployment-agnostic API
integration tests SyntheticsCustomStatusRule \"after all\" hook in
\"SyntheticsCustomStatusRule\" (#225090)\n\n## Summary\n\nIt fixes
#224778\n✅ Falky test
runner\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8441\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ]
...","sha":"e140d226bd07fb429b13839084140013ccb0ecf6"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co>

Resolves #241490

- Followed same approach as the
[fix](#225090) for another similar
failing test which is adding `conflicts: 'proceed'` in `deleteByQuery`
to avoid throwing error in case of conflict deleting documents.