Allow 1.x.x overwrite in config-controller

[kopiczko]

Capo MCs are dynamic and we use giantswarm/config "auto" branches (in format INSTALLATION_auto_config) to not pollute main with commit flood.

But that doesn't work with release apps that have installation specific overwrites as by default config-controller takes latest 1.x.x. We can't use config.giantswarm.io/version in Chart.yaml because that would work with only single installation.

Possible solution here is adding a flag to make config-controller replace 1.x.x with custom ref.

[kubasobon]

config-controller will die in the future, so my approach is add anything to your heart's content.

[tfussell]

I think this issue can be closed. We don't use any MC apps managed by release-operator in OpenStack v20.0.0-alpha1 release https://github.com/giantswarm/releases/blob/master/openstack/v20.0.0-alpha1/release.yaml#L28-L31 so there are no Config CRs involved.

[cornelius-keller]

Closing. Reopen if needed.