Port conflicts caused by barman-cloud sidecar

The Barman Cloud Plugin is injected as an Instance Manager sidecar plugin in the PG Pods. The sidecar starts a controller-runtime manager, which by default, runs a set of http servers for exposing a variety of utilities, such as readiness probes and metrics endpoints.
The way [Kubernetes builds the Network for containers in the same Pod](https://kubernetes.io/docs/concepts/workloads/pods/#pod-networking), doesn't let two processes use the same port even across different containers.

This prevents other processes in other containers to use network ports already used by the barman cloud sidecar, which might be inconvenient if changing them is not straight forward.

The `instance` subcommand should expose additional options to either configure the controller-runtime manager used ports or disable the exposed servers.

Comienza localizando el subcomando `instance` y la configuración del manager de controller-runtime descritos en el issue. Inspecciona cómo están configurados sus servidores HTTP y puertos, y después define cómo el subcomando puede configurarlos o deshabilitarlos; se considera terminado cuando el sidecar ya no provoca conflictos de puertos y las opciones seleccionadas están expuestas mediante el comando instance.

Escrito por el modelo de indexación a partir del texto del issue.