fix(helm): version-agnostic schema-error assertions in the secret-length suite

Helm v4 phrases schema rejections as 'minLength: got N, want 32' while
v3 says 'String length must be greater than or equal to 32'. The suite
grepped for 'minLength' only, so it passed on local helm v4 and failed on
CI's v3.16.4 — the enforcement itself works on both. Patterns now assert
the key name plus either wording. Caught by the new Helm Chart workflow
on its very first run.

Author: waleedlatif1

helm/sim/tests/schema-secret-length_test.yaml

@@ -13,7 +13,7 @@ tests:
       postgresql.auth.password: xxxxxxxx
     asserts:
       - failedTemplate:
-          errorPattern: "BETTER_AUTH_SECRET.*minLength"
+          errorPattern: "BETTER_AUTH_SECRET.*(minLength|greater than or equal to 32)"
 
   - it: rejects an ENCRYPTION_KEY shorter than 32 characters
     set:
@@ -24,7 +24,7 @@ tests:
       postgresql.auth.password: xxxxxxxx
     asserts:
       - failedTemplate:
-          errorPattern: "ENCRYPTION_KEY.*minLength"
+          errorPattern: "ENCRYPTION_KEY.*(minLength|greater than or equal to 32)"
 
   - it: rejects a postgresql.auth.password shorter than 8 characters
     set:
@@ -35,7 +35,7 @@ tests:
       postgresql.auth.password: short
     asserts:
       - failedTemplate:
-          errorPattern: "password.*minLength"
+          errorPattern: "password.*(minLength|greater than or equal to 8)"
 
   - it: accepts an empty BETTER_AUTH_SECRET (deferred to existingSecret/ESO)
     templates: