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, 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.

首先定位 issue 中描述的 instance 子命令和 controller-runtime manager 设置。检查其 HTTP 服务器和端口是如何配置的，然后定义子命令如何配置或禁用它们；完成的标准是 sidecar 不再导致端口冲突，并且所选选项可通过 instance 命令使用。