Handle submission delete

[jmgasper]

We are working at enabling submission delete on the platform, and it's working, but the submission delete isn't being synced through the legacy submission processor down to OR.

That means that submissions deleted from the platform are still showing in OR, which we need to resolve.

The submission delete will raise a submission.notification.delete message in Kafka - we just need to update this legacy-submission-processor to properly handle the message and delete the submission from Informix as well so that it doesn't show up in OR anymore.

NOTE - You will likely need to also update https://github.com/topcoder-platform/legacy-processor-module to expose a deleteSubmission function.

Testing

For testing, you can use jgasperMobile12 / Appirio123 and this challenge:

https://www.topcoder-dev.com/challenges/832c034a-d09a-43b9-9bdd-1efff6dbb485/my-submissions

Feel free to submit and the delete the submissions using the enabled delete button in the UI under ACTIONS on the my-submissions page.

You can see the submission.notification.delete messages in lauscher.

Sample

{
  "resource": "submission",
  "id": "a5c75919-11df-4c7d-9f09-386767730958"
}