ReconciliationSource resources using the restic mover will silently fail under certain conditions.

[benfiola]

Describe the bug
It appears that that the restic has a code path where errors are inadvertently suppressed. This code path includes cases where a ReplicationSource might have invalid data - which was the case when I accidentally left spec.restic.copyMethod unset. Ultimately, I had to clone the repo locally and run the controller with a debugger to determine why this resource was failing to reconcile.

Steps to reproduce
Create a ReplicationSource using restic but without setting spec.restic.copyMethod.

Expected behavior
The resource should be reconciled (e.g., the data moving jobs should be created).

Actual results
The resource is updated to the Transitioning state and then nothing happens.

[tesshuflower]

Fixed by @benfiola in #1455