Changes to PostgresVersion image don't propagate to Postgres resource

for example, while trying to integrate with KubeDB custom PostgresVersion

apiVersion: catalog.kubedb.com/v1alpha1
kind: PostgresVersion
metadata:
  name: postgis-2.5.2
spec:
  version: 9.6
  db:
    image: "localhost:32001/postgres:postgis-2.5.2"
  exporter:
    image: "kubedb/postgres_exporter:v0.4.7"
  tools:
    image: "kubedb/postgres-tools:9.6-v3"

The image name is mistakenly determined as "postgis-2.5.2" instead of "postgres:postgis-2.5.2"

Start by reproducing the issue with the PostgresVersion manifest in the report, then trace how its db.image value is transferred to the Postgres resource. Done means the resulting resource preserves the complete image value, including the registry and postgres: prefix, rather than using only the PostgresVersion name.