E2E non-knownflake fail should print prior error

[kaovilai]

Flake fail should print why tests fail and why it's being retried from prior run instead of "No known FLAKE found in a previous run, marking test as failed."

It should save a prior error and print out during Fail() call

	DescribeTable("Backup and restore applications",
		func(brCase BackupRestoreCase, expectedErr error) {
			if CurrentSpecReport().NumAttempts > 1 && !knownFlake {
				Fail("No known FLAKE found in a previous run, marking test as failed.") // <--
			}

[shubham-pampattiwar]

++

[mateusoliveira43]

The request is partially wrong. When code enters if, it fails immediately, which is the case when knownFlake is false, which means none of these https://github.com/openshift/oadp-operator/blob/master/tests/e2e/lib/flakes.go#L38-L49 occurred. Example of flake happening and being retryed https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_oadp-operator/1294/pull-ci-openshift-oadp-operator-master-4.12-e2e-test-aws/1752417708428759040/artifacts/e2e-test-aws/e2e/build-log.txt

Message "No known FLAKE found in a previous run, marking test as failed." only appears when none of the items in the list happened, and test fails immediately. Example of this behavior https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_oadp-operator/1287/pull-ci-openshift-oadp-operator-master-4.13-e2e-test-aws/1751242762205794304/artifacts/e2e-test-aws/e2e/build-log.txt

@mpryc for your information

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kaovilai]

/lifecycle frozen