[installer]: promote proxy service type from experimental

[mrsimonemms]

Anyone relying upon this config in the experimental section should move to the components. See description for new format

Description

Deprecated the proxy's service type in experimental and promotes it to the primary configuration. Implements the configuration as per #10983.

Includes the KOTS config section in a separate "Components" group - the reasoning behind this is that there may be additional component-specific configuration in the future. This should make it easier to manage/visualise. This is only displayed if the "enable additional options" is enabled.

Adds the ability to deprecate config parameters.

I've also renamed "additional options" to "advanced options"

Related Issue(s)

Fixes #11008
Fixes #11009
Fixes #11025
Fixes #11033

How to test

Release Notes

[installer]: promote proxy service type from experimental

Documentation

Werft options:

• /werft with-preview

[mrsimonemms]

/werft run no-preview publish-to-kots

👍 started the job as gitpod-build-sje-installer-clusterip.2
(with .werft/ from main)

[mrsimonemms]

Based upon @geropl's feedback, this PR has introduced the ability to deprecate fields from the Installer config which prints a deprecation notice to stderr and have added the experimental.webapp.proxy.serviceType param to it

[corneliusludmann]

I have a comment regarding overwriting the experimental config with the new config together with the KOTS UI change. I think that could break the installation when users have a config patch that set the serviceProxy in the experimental section because this will be overwritten by the new proxy config in any case (solely by updating Gitpod with KOTS). I think we need at least a warning, better a property way to handle this.

The remaining comments are my 2 cents only. Feel free to disagree and ignore.

[mrsimonemms]

Ok, I've updated this so it has @corneliusludmann's elegant proposal of dealing with the experimental values.

I've also changed the KOTS config so that the LoadBalancer option doesn't actually set any value. This is so that it doesn't silently break the workflow for anyone upgrading who is using the experimental version already.

I want to refactor how the KOTS config is generated with the config patch file. Deprecations will come in that

[corneliusludmann]

Love it. 🤩

Thanks for taking my suggestions into consideration. 🙏

[geropl]

Nice pattern, thank you @mrsimonemms !

[mrsimonemms]

Team effort - couldn't have done it without you two