configurable namespace for a pluginconfig release

[auhlig]

Closes #50.

[auhlig]

That post-#112 rebase was slightly painful

[auhlig]

rebased & force-pushed

[auhlig]

squashed history after triple rebase was required

[auhlig]

Getting the input device is not a TTY in the license check.

[auhlig]

rebased again to incorporate ci fix

[IvoGoman]

There are some mentions of plugin.Namespace in calls to clientutil.NewRestClientGetterFromRestConfig(..) and helm.ExportNewHelmAction(..)
Could you adapt these to use plugin.ReleaseNamespace as well. This is to avoid unwanted side-effects if in the future the ReleaseNamespace on the test resources is changed.

[auhlig]

There are some mentions of plugin.Namespace in calls to clientutil.NewRestClientGetterFromRestConfig(..) and helm.ExportNewHelmAction(..)
Could you adapt these to use plugin.ReleaseNamespace as well. This is to avoid unwanted side-effects if in the future the ReleaseNamespace on the test resources is changed.

Sure. I'll double check
Some plugin.Namespace references are to remain though, e.g. when resolving option values from a secret next to the plugin we need the plugin namespace, not the release namespace in the remote cluster, etc.