Eventing Manager only uses generic labels for its runtime components

[k15r]

Description

only generic labels are used on runtime components deployed by eventing manager (or lifecycle manager for eventing-manager) to relate those component to the eventing manager.

Acceptance

• no generic labels are used on any of the eventing-manager components
• labels can be used to distinguish clearly between components related to eventing-manager and other components
• upgrading from previous versions of the eventing-manager works
• labels are consistent
• resources created by the eventing-manager are labeled with app.kubernetes.io/created-by: eventing-manager
• labels follow standards are documented here or here

if updating selectors is not supported at the moment (eg for deployments created for the EPP) just update the labels on the deployment, and in the pod template, but leave updating the actual selector to a followup ticket

[marcobebway]

For the time being, we added common labels for the resources managed by the Eventing manager.
Updating the selectors will happen in a later ticket which should focus on doing the update without downtime.