Run "mark_removed_tasks_as_unrecognized" task after creating test tas…

…ks (#206598)

Fixes: #194208

The test fails because the the task marks the removed task as
unrecognized has run before the test tasks are created.
This PR adds a runSoon request that runs the above task after creating
the test tasks.

x-pack/platform/plugins/shared/task_manager/server/integration_tests/removed_types.test.ts

@@ -28,8 +28,7 @@ jest.mock('../monitoring/workload_statistics', () => {
   };
 });
 
-// FLAKY: https://github.com/elastic/kibana/issues/194208
-describe.skip('unrecognized task types', () => {
+describe('unrecognized task types', () => {
   let esServer: TestElasticsearchUtils;
   let kibanaServer: TestKibanaUtils;
   let taskManagerPlugin: TaskManagerStartContract;
@@ -113,6 +112,10 @@ describe.skip('unrecognized task types', () => {
     taskIdsToRemove.push(removeTypeId);
     taskIdsToRemove.push(notRegisteredTypeId);
 
+    // To be sure that the background task that marks removed tasks as unrecognized has run after the tasks were created
+    const runSoonResponse = await taskManagerPlugin.runSoon('mark_removed_tasks_as_unrecognized');
+    expect(runSoonResponse).toEqual({ id: 'mark_removed_tasks_as_unrecognized' });
+
     await retry(async () => {
       const task = await getTask(kibanaServer.coreStart.elasticsearch.client.asInternalUser);
       expect(task?._source?.task?.status).toBe('unrecognized');