Remove tasks instead of marking them as failed

[mikecote]

Part 1 of #79977.

In this PR, I'm making Task Manager remove tasks instead of updating them with status: failed whenever a task gets marked as failed and never runs again.

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: b95bccd
• Interpreting CI Failures

Failed CI Steps

• FTR Configs #15
• FTR Configs #15
• FTR Configs #49
• FTR Configs #49

Test Failures

• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_alerts_none_actions at space1 should handle bulk delete of one rule appropriately based on id
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_alerts_none_actions at space1 should handle bulk delete of one rule appropriately based on id
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_alerts_none_actions at space1 should handle bulk delete of several rules ids appropriately based on ids
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_alerts_none_actions at space1 should handle delete alert request appropriately when consumer is "alerts"
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_alerts_none_actions at space1 should handle delete alert request appropriately when consumer is "alerts"
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle bulk delete of one rule appropriately based on id
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle bulk delete of one rule appropriately based on id when consumer is the same as producer
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle bulk delete of several rules ids appropriately based on filter
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle bulk delete of several rules ids appropriately based on filter
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle bulk delete of several rules ids appropriately based on ids
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete space_1_all_with_restricted_fixture at space1 should handle delete alert request appropriately when consumer is "alerts"
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete superuser at space1 should handle bulk delete of one rule appropriately based on id
• [job] [logs] FTR Configs #49 / alerting api integration security and spaces enabled - Group 3 Alerts - Group 3 alerts bulkDelete superuser at space1 should handle bulk delete of several rules ids appropriately based on ids
• [job] [logs] FTR Configs #15 / task_manager scheduling and running tasks should allow a failed task to be rerun using runSoon
• [job] [logs] FTR Configs #15 / task_manager scheduling and running tasks should allow a failed task to be rerun using runSoon

Metrics [docs]

✅ unchanged

History

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

cc @mikecote