V2 nonkube connector CLI

[lynnemorrison]

Add Connector CLI commands for nonkube implementation
includes create, update status and delete.

[lynnemorrison]

@nluaces
For unit tests I created a dummy test file and then deleted it after test. Want to verify this is acceptable.
.

[nluaces]

timeout flag is specified in refdog for nonkube but not sure how that is used.
The timeout flag should be not used for now, giving that there is no controller for non kube environments. I suggest to hide it for the non_kube implementations.

Regarding the custom resource handler interface, remember to write implementations (empty if it is necessary) to all the resources that implement the interface (i.e. if you implement the List method for connectors, you also need to create the List method in sites)

[fgiorgetti]

This method is called Update, but it is actually just retrieving a connector.
Should it be named something else?

[nluaces]

I missed this, I agree that Update should update a resource.

[lynnemorrison]

will add new issue to fix

[fgiorgetti]

Update does not seem like an appropriate name for what this method is doing.
Maybe we could tweak the Get signature allowing some options to be passed
that indicates if it must read from runtime first or from input only?

[nluaces]

Following the go client for kubernetes as example, the get command interface could be modified to something like this:

Get(name string, opts GetOptions) T

type GetOptions struct {
// runtimeFirst bool
// ...
}

[lynnemorrison]

Will add a new issue to modify the Get command.

[lynnemorrison]

#1777

[fgiorgetti]

Other than my comments and minor suggestions above, it is working just fine.
Thank you!