CLI replication create & delete

[JohnStrunk]

Describe what this PR does
Adds the create and delete commands to the kubectl-volsync replication sub-command

Is there anything that requires special attention?

Related issues:

[codecov]

Codecov Report

Merging #123 (9b3b611) into main (f84d09f) will decrease coverage by 1.0%.
The diff coverage is 48.6%.

@@           Coverage Diff           @@
##            main    #123     +/-   ##
=======================================
- Coverage   73.4%   72.4%   -1.1%     
=======================================
  Files         19      22      +3     
  Lines       1889    2000    +111     
=======================================
+ Hits        1387    1448     +61     
- Misses       396     438     +42     
- Partials     106     114      +8     

Impacted Files	Coverage Δ
kubectl-volsync/cmd/replication_delete.go	5.0% <5.0%> (ø)
kubectl-volsync/cmd/replication_create.go	8.3% <8.3%> (ø)
kubectl-volsync/cmd/replication.go	63.5% <63.5%> (ø)
kubectl-volsync/cmd/relationship.go	75.6% <100.0%> (+9.0%)	⬆️
controllers/mover/restic/mover.go	79.6% <0.0%> (+0.8%)	⬆️

[JohnStrunk]

/retitle CLI replication create & delete

[JohnStrunk]

/cc @v-harihar

[vh05]

@JohnStrunk , This PR provides the skeleton for replication CLI and not the complete implemenation. Am I right ?

[JohnStrunk]

Just create and delete. There are 2 others: set source/destination, and one that has schedule/sync. It's the last of those that actually apply objects to the cluster.

[vh05]

Just create and delete. There are 2 others: set source/destination, and one that has schedule/sync. It's the last of those that actually apply objects to the cluster.

Makes sense.

[vh05]

lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JohnStrunk, v-harihar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [JohnStrunk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vh05]

There are few minor comments like moving the imports and struct member names. But those can be taken care/corrected in full implementation of replication cmds.