Fix keyword routing in values.yaml: field names and decision types

CRITICAL BUG FIX: The values.yaml file is what actually gets deployed
to Kubernetes via Helm, not config.yaml. Fixed both issues:

1. keyword_rules: changed 'category:' to 'name:' (3 rules)
   - urgent_request, sensitive_data, exclude_spam

2. decision conditions: changed type from 'domain' to 'keyword' (3 decisions)
   - urgent_request_decision, sensitive_data_decision, exclude_spam_decision

Root cause: The config.yaml was just a reference file. The actual
deployment uses values.yaml which had the same bugs - keyword rules
were not being loaded at all.

Author: szedan-rh

e2e/profiles/routing-strategies/values.yaml

@@ -53,15 +53,15 @@ config:
       pii_mapping_path: "models/pii_classifier_modernbert-base_presidio_token_model/pii_type_mapping.json"
 
   keyword_rules:
-    - category: "urgent_request"
+    - name: "urgent_request"
       operator: "OR"
       keywords: ["urgent", "immediate", "asap", "emergency"]
       case_sensitive: false
-    - category: "sensitive_data"
+    - name: "sensitive_data"
       operator: "AND"
       keywords: ["SSN", "social security number", "credit card"]
       case_sensitive: false
-    - category: "exclude_spam"
+    - name: "exclude_spam"
       operator: "NOR"
       keywords: ["buy now", "free money"]
       case_sensitive: false
@@ -135,7 +135,7 @@ config:
       rules:
         operator: "AND"
         conditions:
-          - type: "domain"
+          - type: "keyword"
             name: "urgent_request"
       modelRefs:
         - model: "qwen3"
@@ -155,7 +155,7 @@ config:
       rules:
         operator: "AND"
         conditions:
-          - type: "domain"
+          - type: "keyword"
             name: "sensitive_data"
       modelRefs:
         - model: "qwen3"
@@ -179,7 +179,7 @@ config:
       rules:
         operator: "AND"
         conditions:
-          - type: "domain"
+          - type: "keyword"
             name: "exclude_spam"
       modelRefs:
         - model: "qwen3"