vrg: remove the use of captureInProgressStatusUpdate

[raghavendra-talur]

captureInProgressStatusUpdate was a function pointer that was an empty
function when the VRG was being reconciled as Primary and a call to
VRGConditionReasonUploading with status false when reconciling as
Secondary in the relocate case.

Simplify the code by removing the function pointer.

• Remove the captureInProgressStatusUpdate parameter from
  kubeObjectsProtect
  kubeObjectsCaptureStartOrResumeOrDelay
  kubeObjectsCaptureStartOrResume
  kubeObjectsGroupCapture.

[nirs]

Regarding the commit message:

captureInProgressStatusUpdate was a function pointer that was an empty
function when the VRG was being reconciled as Primary and a call to
VRGConditionReasonUploading with status false when reconciling as
Secondary in the relocate case.

This is does not match the code. Previously this code did not consider the action. calling kubeObjectsProtectSecondary() sent a function caling kubeObjectsCaptureStatusFalse() regardless of the action.

This change call kubeObjectsCaptureStatusFalse() only during relocate. It may be correct due to the way we call kubeObjectsProtectSecondary() but it is not a refactoring - you changed the behavior. If you want to change the behavior do this in another commit explaining the change.

[nirs]

To keep the behviour of the previous code, remove the check for action == relocate.

To keep the code simpler and easier to follow, it will help to more the condition into v.kubeObjectsCaptureStatusFalse - we can always call it and it will do the right thing based on the vrg replication state.