Delete of in-progress container is triggered twice

[anatbal]

Describe the bug
When approving/rejecting airlock request the container of in-progress is deleted and then tries to re-delete even though it is already deleted. That occur since the Blob.Created Az Function is triggered on both Blob.Created and Blob.Deleted events (the ip event grid system topic is subscribed to both events).
The solution will be to unregister it from Blob.Deleted events and keep only Blob.Created events.

[anatbal]

@migldasilva

[marrobi]

@anatbal can you confirm this is just the deletion of these lines?

AzureTRE/airlock_processor/BlobCreatedTrigger/function.json

Lines 20 to 26 in 8d97039

	{
	"type": "eventGrid",
	"name": "dataDeletionEvent",
	"topicEndpointUri": "EVENT_GRID_DATA_DELETION_TOPIC_URI_SETTING",
	"topicKeySetting": "EVENT_GRID_DATA_DELETION_TOPIC_KEY_SETTING",
	"direction": "out"
	}