fix: align mongo/k8s/0.2 size schema with TF and make service host-anti-affinity optional

Two module-schema bugs that caused false-positive pre-flight validation
errors (raptor create release) while the platform/Deployer accepts the
specs fine.

mongo/k8s/0.2: the size schema declared `cpu`/`memory` (required), but the
v0.2 Terraform (facets-iac .../1_input_instance/mongodb/main.tf) reads
`cpu_requests`/`memory_requests` behind a `contains(keys, "cpu_requests")`
guard. The `cpu`/`memory` naming only belongs to the 0.3 TF. As a result a
blueprint following the 0.2 schema would silently get NO resource requests,
and a correct blueprint (using cpu_requests/memory_requests, as prod does)
fails validation with "spec.size.memory required field is missing". Rename
the request fields to cpu_requests/memory_requests so the schema matches the
v0.2 module and real usage; limit fields and their x-ui-compare refs updated
to match.

service/deployment/0.1: `enable_host_anti_affinity` was in the spec
`required` list with no default, but the shared app-chart helm template
guards it with `hasKey` and treats absence as "no anti-affinity". The field
is behaviorally optional, so requiring it rejects valid specs (e.g.
service/control-plane-ui). Remove it from `required` (kept in properties and
x-ui-order). Follows the precedent of #520 (health_checks made optional).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: anujhydrabadi

modules/mongo/k8s/0.2/facets.yaml

@@ -42,7 +42,7 @@ spec:
           maximum: 10
           x-ui-placeholder: "e.g., 1 or 3"
           x-ui-error-message: "Instance count must be between 1 and 10."
-        cpu:
+        cpu_requests:
           type: string
           title: CPU Request
           description: Number of CPU cores required.
@@ -54,7 +54,7 @@ spec:
             x-ui-error-message: "CPU cannot be more than CPU limit"
           x-ui-placeholder: "e.g., '500m' or '1'"
           x-ui-error-message: "Value doesn't match pattern, it should be number ranging from 1 to 32 or 1m to 32000m"
-        memory:
+        memory_requests:
           type: string
           title: Memory Request
           description: Amount of memory required.
@@ -73,7 +73,7 @@ spec:
           minLength: 1
           pattern: "^([1-9]|[12][0-9]|3[0-2])$|^(3[0-1][0-9]{3}|[1-2][0-9]{4}|[1-9][0-9]{0,3}|32000)m$"
           x-ui-compare:
-            field: spec.size.cpu
+            field: spec.size.cpu_requests
             comparator: ">="
             x-ui-error-message: "CPU limit cannot be less than CPU"
           x-ui-placeholder: "e.g., '500m' or '1'"
@@ -85,7 +85,7 @@ spec:
           minLength: 1
           pattern: "^(0\\.[1-9]|[1-9](\\.[0-9]+)?|[1-5][0-9](\\.[0-9]+)?|6[0-4])Gi$|^([1-9](\\.[0-9]+)?|[1-9][0-9]{1,3}(\\.[0-9]+)?|[1-5][0-9]{4}(\\.[0-9]+)?|6[0-3][0-9]{3}(\\.[0-9]+)?|64000)Mi$"
           x-ui-compare:
-            field: spec.size.memory
+            field: spec.size.memory_requests
             comparator: ">="
             x-ui-error-message: "Memory limit cannot be less than memory"
           x-ui-placeholder: "e.g., '800Mi' or '1.5Gi'"
@@ -100,8 +100,8 @@ spec:
           x-ui-error-message: "Volume must be specified in the correct format with integer only (e.g., '10Gi' or '50Gi')."
       required:
         - instance_count
-        - cpu
-        - memory
+        - cpu_requests
+        - memory_requests
     backup_configuration:
       type: object
       title: Backup Configuration
@@ -161,7 +161,7 @@ sample:
     authenticated: true
     mongodb_version: 6.0.2
     size:
-      cpu: 2001m
-      memory: 900MiB
+      cpu_requests: 2001m
+      memory_requests: 900Mi
       volume: 8G
       instance_count: 3

modules/service/deployment/0.1/facets.yaml

@@ -1757,7 +1757,6 @@ spec:
           - runtime
   required:
   - restart_policy
-  - enable_host_anti_affinity
   - runtime
   x-ui-order:
   - restart_policy