Implement initial Eventing-manager using Kubebuilder

[k15r]

Description

As we start from scratch the first step to a fully implemented eventing module is handling the CR. Handling the CR consists of two parts.

1. Lifecycle manager deploys the module and determines its state using the state field in the status subresource.
2. Eventing-Manager reacts to the Eventing-CR and updates the state field in the status subresource.

After implementation of this ticket the eventing module will be considered ready by the lifecycle manager. At this time no actual eventing related behaviour is active.

Tasks to be implemented

• Scaffold a new controller using kubebuilder #4

Acceptance:

• No actual resources need to be active (api rules, deployments, services).

[mfaizanse]

Closing in favor of main EPIC (#2)