HelmRepo channel and subscriptions do not support relative urls in helm chart index.yaml

[eformat]

we have been testing against multiple helm chart repositories and it appears that charts repos that specify relative url's in their index.yaml cannot be deployed by open cluster manager

nexus for example creates relative urls

-- nexus helm-chart index.yaml

apiVersion: v1
entries:
  pet-battle-api:
  - appVersion: 1.0-SNAPSHOT
    created: 2020-05-18T04:45:49.800Z
    description: A Helm chart for Kubernetes
    digest: 414ad02c1e957ad078ec069c4d64e4b32a45bc3526d38f1a40e942c7807c1537
    maintainers:
    - name: eformat
    name: pet-battle-api
    urls:
    - pet-battle-api-1.0.0.tgz
    version: 1.0.0
generated: 2020-05-22T01:23:13.395Z

-- helm generated index.yaml

apiVersion: v1
entries:
  pet-battle-api:
  - apiVersion: v2
    appVersion: 1.0.0
    created: "2020-05-22T12:36:52.297103117+10:00"
    description: A Helm chart for Kubernetes
    digest: 73bb90bc3e1f517eb4d97be5184d0abaf245a19c1984586792f76bb38c592421
    home: https://eformat.github.io/helm-charts
    maintainers:
    - name: eformat
    name: pet-battle-api
    type: application
    urls:
    - https://eformat.github.io/helm-charts/pet-battle-api-1.0.0.tgz
    version: 1.0.0
generated: "2020-05-22T12:36:52.283165021+10:00"    

it appears that helm3 supports either type using the --url flag when creating the index.yaml

when using the nexus repo - the error in ocm tracks back to here:

{Irreconcilable True ReconcileError failed to download chart from helm repo. - url: pet-battle-api-1.0.0.tgz error: unsupported scheme 2020-05-21 23:50:58 +0000 UTC}] }}

https://github.com/open-cluster-management/multicloud-operators-subscription-release/blob/master/pkg/utils/helmrepoutils.go#L240

given the Channel definition already specifies the helm repo pathname, is it possible to support relative urls in ocm ?