v1.7.0: Merge pull request #288 from java-operator-sdk/client-v5

The 1.7.0 release updates to the 5.0.0 version of the fabric8 Kubernetes client. While this should improve the user experience quite nicely, there are a couple of things to be aware of when upgrading from a previous version as detailed below:

• Doneable classes have been removed along with all the involved complexity
• Controller annotation has been simplified: the crdName field has been removed as that value is
  computed from the associated custom resource implementation
• Custom Resource implementation classes now need to be annotated with Group and Version
  annotations so that they can be identified properly. Optionally, they can also be annotated with
  Kind (if the name of the implementation class doesn't match the desired kind) and Plural if
  the plural version cannot be automatically computed (or the default computed version doesn't match
  your expectations).
• The CustomResource class that needs to be extended is now parameterized with spec and status
  types, so you can have an empty default implementation that does what you'd expect. If you don't
  need a status, using Void for the associated type should work.
• Custom Resources that are namespace-scoped need to implement the Namespaced interface so that
  the client can generate the proper URLs. This means, in particular, that CustomResource
  implementations that do not implement Namespaced are considered cluster-scoped. As a
  consequence, the isClusterScoped method/field has been removed from the appropriate
  classes (Controller annotation, in particular) as this is now inferred from the CustomResource
  type associated with your Controller.

Many of these changes might not be immediately apparent but will result in 404 errors when
connecting to the cluster. Please check that the Custom Resource implementations are properly
annotated and that the value corresponds to your CRD manifest. If the namespace appear to be missing
in your request URL, don't forget that namespace-scoped Custom Resources need to implement
the Namescaped interface.