[openVSXProxy] Mark the usage of PVC optional

Fixes #14529 Currently, OpenVSXProxy is the only non-optional component that needs PVC's to get things working. The usage of a PVC in AWS reference architecture, means that components can't get restarted in a different zone anymore as PVC's with EBS are specific to a zone. As EKS reference architecture does not enable any other component that uses PVC's (i.e minio), This is a problem specific to `OpenVSXProxy`. By disabling this, OpenVSXProxy's redis now will have lost the cache once a restart occurs which does not seems like a big deal for self-hosted customers. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>

Author: Pothulapati

install/installer/cmd/testdata/render/vsxproxy-pvc/config.yaml

@@ -0,0 +1,8 @@
+# Copyright (c) 2022 Gitpod GmbH. All rights reserved.
+# Licensed under the MIT License. See License-MIT.txt in the project root for license information.
+
+apiVersion: v1
+domain: gitpod.example.com
+openVSX:
+ proxy:
+ disablePVC: true