Use uniquely identifying labels selector for the operator deployment

[astefanutti]

This PR changes the operator deployment to use a uniquely identifying labels selector.

In order to work-around the immutability of the labels selector field, the deployment has been renamed according to OLM recommendation: operator-framework/operator-lifecycle-manager#952 (comment).

This PR also leverages Kustomise commonLabels config, to apply Kubernetes recommended labels to all resources.

Fixes #112.

[astefanutti]

/assign @anishasthana @Maxusmusti

[astefanutti]

I've tested the change, by building an updated OLM catalog image, containing a newer version (0.0.3-dev) of the operator OLM bundle with the fix, replacing the latest bundle (0.0.3) in the default channel, which has triggered an automated upgrade:

I confirm renaming the operator deployment makes OLM performing a delete / create operation, instead of an update, which effectively by-passes the immutability of the deployment labels selector.

Before (version 0.0.3):

After (version 0.0.3-dev):

This also fixes the monitoring service pods selection:

[anishasthana]

/lgtm

Thanks @astefanutti

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anishasthana

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [anishasthana]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment