Simpler way to handle fw-headless volume size

Now we allocate 10 GiB everywhere, except 20 on staging and 150 GiB on
production (similar size to hg-repos volume since we could potentially
end up with copies of everything from hg-repos).

deployment/production/fw-headless-volume.yaml

@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: hg-repos
+  namespace: languagedepot
+spec:
+  resources:
+    requests:
+      storage: 150Gi

deployment/production/kustomization.yaml

@@ -9,6 +9,7 @@ resources:
 patches:
   - path: lexbox-deployment.patch.yaml
   - path: app-config.yaml
+  - path: fw-headless-volume.yaml
   - path: hg-repos-volume.yaml
   - path: hg-deployment.yaml
   - path: ingress-config-prod.yaml

deployment/staging/fw-headless-volume.yaml

@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: fw-headless
+  namespace: languagedepot
+spec:
+  resources:
+    requests:
+      storage: 30Gi

deployment/staging/kustomization.yaml

@@ -7,6 +7,7 @@ resources:
 components:
   - ../init-repos
 patches:
+  - path: fw-headless-volume.yaml
   - path: fw-headless-deployment.patch.yaml
   - path: lexbox-deployment.patch.yaml
   - path: app-config.yaml