(WIP) refactor: use operator sdk

[tylerslaton]

Summary

When this repository was originally built, it was not considered to use the operator-sdk. As its lifecycle is moving closer to becoming a bundle (and eventually included in the default catalog), it started to become clear that the tooling that the operator-sdk provides would be good to bring into this.

This is good for a number of reasons as the repo can now:

1. Easily build bundles
2. Adhere to a common bundle structure
3. Be validated and operated on by the operator-sdk

From this, we are also able to start finalizing the bundle structure and images for Combo. Moving forward, new operator-framework containers exist inside of quay.io.

• quay.io/operator-framework/combo-operator
• quay.io/operator-framework/combo-bundle

Using the bundle image built in this repo (current quay.io/operator-framework/combo-bundle:v0.0.1), I was able to add it to a catalog and a subscription to the bundle. From there the operator acted as expected.

How was this done?

To start this, I created a default repo as defined by operator-sdk init. From there, I went and started adding the combo specific features, api's, packages - etc. Somethings that are not default from the init are:

1. The Makefile has more targets.
2. CI/CD is carried over from the original repository.
3. E2E suite is defined in the root test directory.

TODO:

• [ ] Bring over the CLI binary structure
• [ ] Validate bundle format is how we want moving forward
• [ ] Establish a process for incrementing bundle/operator versions

Closes #67 Close #71

[openshift-ci[bot]]

@tylerslaton: PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.