[initializer] Replace `GIT_SSL_CAINFO` with `GIT_SSL_CAPATH`

Fixes gitpod-io#10173

Using `GIT_SSL_CAPATH` means that we will continue to support
publicly signed SCM's even when we have a `customCA` configured.

Signed-off-by: Tarun Pothulapati <[email protected]>

[initializer] Replace `GIT_SSL_CAINFO` with `GIT_SSL_CAPATH`

Fixes gitpod-io#10173

Using `GIT_SSL_CAPATH` means that we will continue to support
publicly signed SCM's even when we have a `customCA` configured.

Signed-off-by: Tarun Pothulapati <[email protected]>

May 2022 Gitpod release

[ws-daemon] Support GIT_SSL_CAINFO

[ws-daemon] Support GIT_SSL_CAINFO

[kots]: delete any existing openvsx-proxy stateful set

Update `registry-facade` to use `https-certificate`

THis updates the `GITPOD_CA_CERT` loading to also use the same customCA
cert, instead of loading `builtin-registry-facade-cert` which is not
used anywhere for now.

This is done to fix the GKE regression of loading certs into
`docker` and `containerd`.

Signed-off-by: Tarun Pothulapati <[email protected]>

[code]: update stable to 1.66.2

Copy of gitpod-io#9381 for hotfix release

[code]: update stable to 1.66.2

Copy of gitpod-io#9381 for hotfix release

[auth] fix missing updates to dynamic login providers

this primarily affects self-hosted installation where the `ownerId` is about to change during the initial setup of the login/git provider.