Fix client validate_reimbursements_for_llm to match SaaS behavior

BCBS: change strict == "YES" to "YES" in final_answer. The strict
equality was rejecting borderline LLM responses (e.g. "YES, ..."),
dropping row counts from ~7 to 1.

Clover: remove .strip().upper() which crashed with AttributeError
because the parser returns a list, not a string. Every validation
call failed, dropping row counts from 106 to 1.

Both overrides now use the same "YES" in final_answer logic as SaaS.
E2E verified: BCBS 5 rows (within LLM variance of baseline 7),
Clover 106 rows (exact match to baseline).

src/pipelines/clients/bcbs_promise/prompts/prompt_calls.py

@@ -50,4 +50,4 @@ def validate_reimbursements_for_llm(answer_dict: dict[str, str], filename: str)
         f"LLM response for reimbursement validation in {filename}:\n{llm_response}"
     )
     final_answer = _parser(llm_response)
-    return final_answer == "YES"
+    return "YES" in final_answer

src/pipelines/clients/clover/prompts/prompt_calls.py

@@ -49,5 +49,5 @@ def validate_reimbursements_for_llm(answer_dict: dict[str, str], filename: str)
     logging.debug(
         f"LLM response for reimbursement validation in {filename}:\n{llm_response}"
     )
-    final_answer = _parser(llm_response).strip().upper()
-    return final_answer == "YES"
+    final_answer = _parser(llm_response)
+    return "YES" in final_answer