Utilise Object Lifecycle Management when deleting resources in GCS

[TobyPinfold]

Is your feature request related to a problem? Please describe.

When deleting a pipeline the provider workflow is using the GCS client to iterate over each file within the bucket and trigger a delete operation on them. This leads to issues when a pipeline is long lived with many compilations as it the number of files to be deleted takes enough time for the workflow to timeout, leaving a state whereby some files are deleted and some are still existing, requiring manual intervention.

Describe the solution you'd like

Instead of iterating over a gcs bucket contents we should follow the suggestions made by google to delete all bucket contents asynchronously by setting the Object Lifecycle Management Age of the bucket to 0 days.

Additional context
Mainly impacts the use of a VAI provider