oadp-1.4 periodic e2e (4.18 AWS): "Multiple BSL with custom CA cert" times out on "Default BSL should be available" #2514

Summary

periodic-ci-openshift-oadp-operator-oadp-1.4-4.18-e2e-test-aws-periodic has failed 12 of its last 20 runs (Oct 1–22). The recurring failure is in the Multiple BSL with custom CA cert tests, not the S3 GetBucketRegion blip tracked in #2512.

Evidence (periodic job, oadp-1.4, 4.18 AWS)

Failure signature (Oct 18):

[FAILED] Timed out after 180.003s.
Default BSL should be available
Expected <bool>: false to be true
In [It] at: tests/e2e/backup_restore_suite_test.go:696
Exit [It] three BSLs with backupImages=false (no CA cert handling) - backup_restore_suite_test.go:741 (3m21s)

Oct 18 run: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-oadp-operator-oadp-1.4-4.18-e2e-test-aws-periodic/2111668852025724928

Not covered here

• The Oct 20 nil-pointer panic in BSLsAreUpdated (tests/e2e/lib/dpa_helpers.go:304) already has fixes: fix(e2e): don't dereference nil BSL LastValidationTime in BSLsAreUpdated #2499, fix: add nil guard for BSL LastValidationTime in BSLsAreUpdated #2500, [oadp-1.5] fix: add nil guard for BSL LastValidationTime in BSLsAreUpdated #2502.
• The S3 region lookup blip (Oct 3, Oct 8, Oct 21): Add S3 GetBucketRegion transient failure to known flakes #2512, plus a retry fix to follow.

To investigate

• Why the default BSL never reaches Available within 180s in this spec on 1.4/4.18: CA cert / backupImages handling, BSL validation timing, or the test's own wait.
• Whether the same spec is flaky on other branches/versions or only 1.4.
• Whether the 180s timeout is too tight for this job's cluster speed (the full e2e takes about 85 min).