Create a Camel CRD

[nicolaferraro]

It is installed together with the operator and contains the global configuration. Each resource created by the operator (Integration, Integration Context) should be a child of the top level resource, so that we can retrieve the global config when processing them.
A side effect is that we can install more Camel K instances in a namespace. In the future we should make sure the work of the operator is minimal (offload builds to a builder pod).

This is compatible with OLM: https://github.com/operator-framework/operator-lifecycle-manager
People can install a "Camel" instane alone (maybe we should find a better name for the top level resource) in a namespace (it will install CR + operator), or install directly a "Integration": the "Integration" can be set to depend on a "Camel" resource, so the installer will setup everything needed for the integration to run.