core chart puts browse_type configurations to two places unnecessarily: registrar_config and init_db

Helm template generates the registrar_config with browse_type definitions but does not need to have it, it is already a part of init_db script. Is it okay to delete the part of chart generating registrar_config browse_types or is there any reason in other (EOEPCA) deployments to do it this way?

these values:

 productTypes:
    - name: NAO_BUN_1A
      browses:
        TRUE_COLOR:
          red:
            expression: red
            range: [50, 1000]
            nodata: 0
          green:
            expression: green
            range: [50, 1000]
            nodata: 0
          blue:
            expression: blue
            range: [50, 1000]
            nodata: 0

generate following init-db part

    python3 manage.py browsetype create "NAO_BUN_1A"  "TRUE_COLOR" \
        --red "red" \
        --green "green" \
        --blue "blue" \
        --red-range 50 1000 \
        --green-range 50 1000 \
        --blue-range 50 1000 \
        --red-nodata 0 \
        --green-nodata 0 \
        --blue-nodata 0 \
        --traceback

and following registrar_config part

        - browses:
           TRUE_COLOR:
              blue:
                expression: blue
                nodata: 0
                range:
                - 50
                - 1000