[Job Launcher] Invalid event types for webhooks

[dnechay]

Describe the bug
Right now JL has next event types enum to validate webhook requests:

enum EventType {
  ESCROW_CREATED = 'escrow_created',
  ESCROW_CANCELED = 'escrow_canceled',
  ESCROW_COMPLETED = 'escrow_completed',
  TASK_CREATION_FAILED = 'task_creation_failed',
  ESCROW_FAILED = 'escrow_failed',
  ABUSE_DETECTED = 'abuse_detected',
}

Processing on JL is supported for next event types:

• EventType.ESCROW_COMPLETED
• EventType.TASK_CREATION_FAILED
• EventType.ESCROW_FAILED

However, what we have in other oracles is a bit different:

• escrow_completed is sent from Reputation Oracle to JL and all good here
• task_creation_failed is sent from Fortune ExcO, but CVAT ExcO sends job_creation_failed
• escrow_failed is not sent in system at all
• escrow_cleaned is sent from CVAT ExcO, but not handled in JL

Expected behavior
Webhook event types should be aligned within the system

[flopez7]

We’ve decided to keep escrow_completed as is. Once @Dzeranov confirms, task_creation_failed will be removed in favor of the standard escrow_failed event for any errors. Additionally, escrow_cleaned will be removed from the CVAT Exchange Oracle to ensure consistent event types across the system

[Dzeranov]

escrow_cleaned is sent from CVAT ExcO, but not handled in JL

Exchange Oracle sends escrow_cleaned only to Recording Oracle so no further actions required.

[Dzeranov]

task_creation_failed is sent from Fortune ExcO, but CVAT ExcO sends job_creation_failed

We should get rid of task_creation_failed on both JL and Fortune oracles and use escrow_failed instead.
CVAT Exchange Oracle will use it as well.