Use k8s' owner reference to delete the temporary data volume

[szczeles]

When a volume is defined in the configuration, first step of the pipeline creates one and on-exit-handler removes it. However, it looks that since Nov 2021 there is way more elegant way to handle it by setting ownerReference on the volume to the Workflow object, so it will be cleaned by K8s GC itself:

kubeflow/pipelines#6649 (comment)

Let's check how it behaves and use it in our plugin if it works as expected