Airlock processor handles request cancellation

[eladiw]

Description

As an Airlock processor in TRE
I want to be able to be able to consume and operate on cancel event
So that requests cancelation are handled

Acceptance criteria

• Data artifact are copied to the 'canceled' containers (import cancel or export cancel)
• Step result event is sent by the airlock processor when the data copy is done
• Data deletion event should be sent (which is handled by Airlock - data cleanup (deletion) when moving between stages #1963 )
• Data Steward can no longer access previously used storage (call method by Airlock - Revoke SAS token #1965 )
• A notification event with all the details sent to Event grid (to be consumed by Airlock - create notification mechanism #1964 )

[eladiw]

@joalmeid @marrobi @yuvalyaron
The story talks about moving the data to a NEW storage accound called cancelled.
I think its an overkill, how about we simply delete the data of a cancelled request.

Reminder, we allow to cancel only in-review requests or draft requests, so its not possible to cancel a rejected or approved requests for example...

[marrobi]

I think so... we don't really want the data hanging around.

[eladiw]

@tamirkamara @yuvalyaron so let's delete the data