Operator dev profile to include registry

### Requirement

Follow up #6756 - the same registry configuration used in test can be used as a side deployment controlled by the operator for development-only environments. If a given flag is enabled (via env var), the operator could run a registry and self configure the registry settings with those values. In this way we have a self contained development environment and we can simplify installation notes and the first approach to new users removing the need to install the registry as a prerequisite.

It's important to mark that this feature would be exclusively usable for development purposes, not for any production workload.

Start by reviewing follow-up issue #6756 and the registry configuration already used in tests. Trace how the operator reads environment-variable flags and controls side deployments. Done means a development-only registry can be enabled, self-configured, and used without a separately installed registry, while remaining unsuitable for production workloads.

Written by the indexing model from the issue text.