Allow Helm Chart Registry to be namespace scoped

Problem

Today, developers don't have any way to pull in their own helm charts to the helm chart catalog.

Goal

Allow developers to create Helm Chart Registries which are namespace scoped, to enable developers to pull in their own helm charts to their namespace.

Why is it important?

Developers want to be able to enable access to their own helm charts in their namespace without having to go the administrator.

Acceptance criteria

1. As a non privileged user, I should be able to connect my Helm Chart Repository to my project, so I can access the Helm Charts from the DevConsole catalog
2. As a non privileged user, I should see a QuickStart which guides me through the process of connecting my HelmChartRepo to my project

UX Design

1. Developers will accomplish this by creating a CR either via YAML editor, Import YAML or even oc apply
2. This new Helm Chart Repository will show up in the faceted filters section in Chart Repositories
   

Dependencies (External/Internal)

Note