Add kustomize deployment

[tylerauerbeck]

This PR adds the ability to deploy the operator using kustomize. This adds a few things of value here:

• Fixes #26 . Because we're able to set a default namespace inside of the kustomization (and thereby anybody who wants to pull this in can set their own desired namespace), you no longer have to use the default namespace to deploy a service account. It will just dynamically replace the namespace for all objects (including the references inside of the ClusterRoleBinding) and deploy it appropriately.
• No extra magic needed to have all manifests added to a single file. Now you can run a single command to deploy the kustomization and it just picks up the appropriate resources (rather than duplicating them).
• Allows others to pull this operator in remotely by using a remote base, which will allow them to base their deployment off of what is contained in this repository (while also being able to customize it to their own needs).

The nice thing about this too is that it also provides a fairly simple deployment strategy. We can run kubectl apply -k deploy/ and it will deploy the resources as we've definied in kustomization.yaml.

I realize this doesn't directly relate to any open issue, but thought it was a useful way to resolve #26. Feel free to close this if this isn't a direction you'd want to head.

[geerlingguy]

This PR is indeed helpful, but I wanted to note that now that the operator is being maintained in the Ansible namespace, I am not going to maintain this project anymore (as I consider it a historic artifact which was used to as a base for the ansible-namespace version, and I'm redirecting all issues and PRs to the Ansible-maintained version: https://github.com/ansible/awx-operator