Possibility to deploy the operator in an arbitrary namespace

Authorino Operator's [deployment manifests](https://github.com/Kuadrant/authorino-operator/blob/main/config/deploy/manifests.yaml), generated using [this](https://github.com/Kuadrant/authorino-operator/blob/785b0777ac031fbd2a10cfa5478831b8db9419b2/Makefile#L171) make target, currently enforce `authorino-operator` as the Kubernetes namespace to run the operator workload.

While on one hand that single-file manifest is very useful to install and deploy the Operator and the CRDs, changing the operator namespace, on the other hand, is not straightforward, requiring all occurrences of `namespace: authorino-operator` in the file, as well as the name of `Namespace` resource itself, to be properly replaced.

Except in the `RoleBinding` and `ClusterRoleBinding` resources, mentioning the Kubernetes namespace could be avoided, but in general, perhaps using a placeholder to ensure assertive replacement (e.g. making possible to rely on envsubst)? Another option would be relying more on [Operator Lifecyle Manager](https://olm.operatorframework.io) to install the operator? Although it's not available by default in Kubernetes, but only in OpenShift.

Start with config/deploy/manifests.yaml and the Makefile target around line 171 that generates it. Trace every namespace reference, including the Namespace, RoleBinding, and ClusterRoleBinding resources, then compare the placeholder/envsubst and OLM approaches described in the issue. Done should mean the operator can be installed in an arbitrary namespace without manual replacements, using one documented approach.

Written by the indexing model from the issue text.