Increase vault pod readiness retry count from 20 to 40

[rhjcd]

Summary

• Doubles the retry count from 20 to 40 for the vault namespace check and vault pod readiness check in roles/vault_utils/tasks/vault_status.yaml
• Extends the maximum wait time from ~15 minutes to ~30 minutes per check (retries x 45s delay)
• Addresses an 18.9% failure rate on RHDP sandbox environments where shared infrastructure causes vault pod startup to exceed the current 15-minute timeout

Context

On Red Hat Demo Platform sandbox environments, vault pod startup frequently takes longer than 15 minutes due to:

• ArgoCD deployment sequencing delays
• PVC provisioning on shared storage
• Operator unseal job timing

The delay interval (45 seconds) is unchanged -- only the retry count increases.

Test plan

• Deploy a validated pattern on a sandbox environment and confirm vault readiness checks succeed within the extended window
• Verify no regression on environments where vault starts quickly (the check still exits as soon as the pod is ready)

[rhpds-bot]

@darkdoc will you review and merge please?