Add the ability to use a custom pvc transfer image for source and destination

[jmontleon]

For downstream we will likely need to use allow using a different rsync-transfer image. Even with a community release it will be necessary in disconnected or restricted networks. We'll need to update the pvc-transfer ClusterTask to accept these options.

Once those PRs are merged and we've decided how to pass them in we should update the ClusterTask to deal with them properly.

Based on current PRs it should look roughly like so:

crane transfer-pvc \
          --source-image=quay.io/jmontleon/rsync-source-transfer:latest \
          --destination-image=quay.io/jmontleon/rsync-transfer:latest \
...

[github-actions]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

[eriknelson]

/triage accepted
/priority normal

[github-actions]

This issue synced with: https://issues.redhat.com/browse/MTRHO-116