Allow specifying PropagationPolicy for deleting k8s resources

[jonapgar-groupby]

Is your feature request related to a problem? Please describe.
Currently, when you delete a resource using a Sensor, the default PropagationPolicy of foreground is used. This means some dependent resources are not deleted. For example, when deleting a job, the pod is not deleted. The failed pods accumulate in k8s.

Describe the solution you'd like
A field in the Sensor resource to specify the PropagationPolicy.

Currently the StandardK8sTrigger does not accept any DeleteOptions:

argo-events/pkg/sensors/triggers/standard-k8s/standard-k8s.go

Line 222 in 0494ce7

err = k8sTrigger.namespableDynamicClient.Namespace(namespace).Delete(ctx, obj.GetName(), metav1.DeleteOptions{})

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.