[9.1] [Security Solution] Unskip prebuilt rule upgrade ML jobs field test (elastic#232758) (elastic#233639)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[Security Solution] Unskip prebuilt rule upgrade ML jobs field test
(elastic#232758)](elastic#232758)

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

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

<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-09-01T13:04:57Z","message":"[Security
Solution] Unskip prebuilt rule upgrade ML jobs field test
(elastic#232758)\n\n**Resolves:
https://github.com/elastic/kibana/issues/220081**\n\n## Summary\n\nThis
PR unskips skipped earlier Prebuilt Rule Upgrade workflow ML jobs field
Jest integration test.\n\n## Details\n\nThe Jest integration test
`Upgrade diffable rule \"machine_learning_job_id\" (machine_learning
rule type) after preview in flyout customized field w/ an upgrade
resulting in a non-solvable conflict (ABC) upgrades rule to resolved
value` was skipped earlier in `9.1` and `9.2` due to flakiness. Since
that moment combobox integration flakiness has been addressed in the
scope of https://github.com/elastic/kibana/pull/228620.\n\nThorough
testing in `main` (corresponds to `9.2`) and `9.1` branches hasn't
revealed any failures or flakiness. On top of that this test runs in
`8.18` and `8.19` smoothly all that time.\n\nTaking the above into
account it should be safe to unskip the skipped test. In case if the
flakiness pops up we'll have more data to
analyze.","sha":"f8992660b97d5e6bc660ac08e241490c63e38764","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.2.0","v9.1.3"],"title":"[Security
Solution] Unskip prebuilt rule upgrade ML jobs field
test","number":232758,"url":"https://github.com/elastic/kibana/pull/232758","mergeCommit":{"message":"[Security
Solution] Unskip prebuilt rule upgrade ML jobs field test
(elastic#232758)\n\n**Resolves:
https://github.com/elastic/kibana/issues/220081**\n\n## Summary\n\nThis
PR unskips skipped earlier Prebuilt Rule Upgrade workflow ML jobs field
Jest integration test.\n\n## Details\n\nThe Jest integration test
`Upgrade diffable rule \"machine_learning_job_id\" (machine_learning
rule type) after preview in flyout customized field w/ an upgrade
resulting in a non-solvable conflict (ABC) upgrades rule to resolved
value` was skipped earlier in `9.1` and `9.2` due to flakiness. Since
that moment combobox integration flakiness has been addressed in the
scope of https://github.com/elastic/kibana/pull/228620.\n\nThorough
testing in `main` (corresponds to `9.2`) and `9.1` branches hasn't
revealed any failures or flakiness. On top of that this test runs in
`8.18` and `8.19` smoothly all that time.\n\nTaking the above into
account it should be safe to unskip the skipped test. In case if the
flakiness pops up we'll have more data to
analyze.","sha":"f8992660b97d5e6bc660ac08e241490c63e38764"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232758","number":232758,"mergeCommit":{"message":"[Security
Solution] Unskip prebuilt rule upgrade ML jobs field test
(elastic#232758)\n\n**Resolves:
https://github.com/elastic/kibana/issues/220081**\n\n## Summary\n\nThis
PR unskips skipped earlier Prebuilt Rule Upgrade workflow ML jobs field
Jest integration test.\n\n## Details\n\nThe Jest integration test
`Upgrade diffable rule \"machine_learning_job_id\" (machine_learning
rule type) after preview in flyout customized field w/ an upgrade
resulting in a non-solvable conflict (ABC) upgrades rule to resolved
value` was skipped earlier in `9.1` and `9.2` due to flakiness. Since
that moment combobox integration flakiness has been addressed in the
scope of https://github.com/elastic/kibana/pull/228620.\n\nThorough
testing in `main` (corresponds to `9.2`) and `9.1` branches hasn't
revealed any failures or flakiness. On top of that this test runs in
`8.18` and `8.19` smoothly all that time.\n\nTaking the above into
account it should be safe to unskip the skipped test. In case if the
flakiness pops up we'll have more data to
analyze.","sha":"f8992660b97d5e6bc660ac08e241490c63e38764"}},{"branch":"9.1","label":"v9.1.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Maxim Palenov <[email protected]>

Author: kibanamachine

x-pack/solutions/security/plugins/security_solution/public/common/test/eui/combobox.ts

@@ -59,9 +59,9 @@ export async function selectEuiComboBoxOption({
         fireEvent.click(optionToSelect);
       } else {
         throw new Error(
-          `Could not find option with text "${optionText}". Available options: ${options
+          `Could not find option with text "${optionText}". Available options: [${options
             .map((option) => option.textContent)
-            .join(', ')}`
+            .join(', ')}]`
         );
       }
     } else {

x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_management_ui/pages/rule_management/__integration_tests__/rules_upgrade/test_utils/assert_rule_upgrade_after_review.ts

@@ -257,8 +257,7 @@ export function assertRuleUpgradeAfterReview({
     });
   });
 
-  // FLAKY: https://github.com/elastic/kibana/issues/220081
-  describe.skip('customized field w/ an upgrade resulting in a non-solvable conflict (ABC)', () => {
+  describe('customized field w/ an upgrade resulting in a non-solvable conflict (ABC)', () => {
     it('upgrades rule to suggested value', async () => {
       mockRuleUpgradeReviewData({
         ruleType,

x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_management_ui/pages/rule_management/__integration_tests__/rules_upgrade/test_utils/set_field_value.ts

@@ -771,6 +771,7 @@ async function inputMachineLearningJobId(
 ): Promise<void> {
   const jobIds = [value].flat();
 
+  // Clear currently selected job
   await clearEuiComboBoxSelection({
     clearButton: within(fieldFinalSide).getByTestId('comboBoxClearButton'),
   });