[EDR Workflows] Stabilize "add a new entry" FTR test under env pressure (elastic#268313)

The `should be able to add a new ${testData.title} entry` parametrized
test in `artifact_entries_list.ts` intermittently fails on Serverless
with a `TimeoutError` waiting for the new artifact's
`criteriaConditions` card to render within the default 10s implicit
wait. Mirrors the sibling update-flow pattern: wraps the post-create
assertion in `retry.waitForWithTimeout(20000, …)` keyed on the
`criteriaConditions` card before running the existing `checkResults`
loop.

Closes elastic#265265

Author: szwarckonrad

x-pack/solutions/security/test/security_solution_endpoint/apps/integrations/artifact_entries_list.ts

@@ -241,7 +241,15 @@ export default ({ getPageObjects, getService }: FtrProviderContext) => {
 
         it(`should be able to add a new ${testData.title} entry`, async () => {
           await createArtifact(testData, { policyId: policyInfo.packagePolicy.id });
-          // Check new artifact is in the list
+
+          // Check new artifact is in the list (wait for list to be updated)
+          await retry.waitForWithTimeout('entry is added to list', 20000, async () => {
+            const currentValue = await testSubjects.getVisibleText(
+              testData.create.checkResults[0].selector
+            );
+            return currentValue === testData.create.checkResults[0].value;
+          });
+
           for (const checkResult of testData.create.checkResults) {
             expect(await testSubjects.getVisibleText(checkResult.selector)).to.equal(
               checkResult.value