failure analysis: mistaken resource apply diff for as root cause of e2e failure.

[kaovilai]

A case might fail on like

  [FAILED] Unexpected error:
      <*errors.StatusError | 0xc00101e640>: 
      container "todolist" in pod "todolist-755b6749cf-vnt2h" is waiting to start: PodInitializing
      {
          ErrStatus: {
              TypeMeta: {Kind: "", APIVersion: ""},
              ListMeta: {
                  SelfLink: "",
                  ResourceVersion: "",
                  Continue: "",
                  RemainingItemCount: nil,
              },
              Status: "Failure",
              Message: "container \"todolist\" in pod \"todolist-755b6749cf-vnt2h\" is waiting to start: PodInitializing",
              Reason: "BadRequest",
              Details: nil,
              Code: 400,
          },
      }
  occurred
  In [AfterEach] at: /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:387 @ 01/13/26 17:32:29.682
  < Exit [AfterEach] Backup and restore tests - /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:422 @ 01/13/26 17:32:29.682 (1.391s)

but analysis got hung up on diff

## Failed Tests Analysis

### 1. Mongo application DATAMOVER [CRITICAL]

**Root Cause**: SecurityContextConstraints (SCC) resource comparison failure after restore - the `allowedVolumes` field was restored with wildcard `["*"]` instead of the original detailed list of volume types.

**Evidence**:
```
junit_report.xml: "[FAILED] No known FLAKE found in a previous run, marking test as failed. In [It] at: /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:456"

Test system-err shows comparison failure:
  []any{
- 	string("awsElasticBlockStore"),
+ 	string("*"),
- 	string("azureDisk"),
- 	string("azureFile"),
- 	string("cephFS"),
- 	string("cinder"),
- 	string("configMap"),
- 	string("csi"),
- 	string("downwardAPI"),
  ... [full list of ~30 volume types replaced with "*"]
  }

must-gather: Restore mongo-datamover-e2e-e0e6ccb2-f0a3-11f0-a143-0a580a828d79 shows "Phase: Completed" but SCC comparison in test failed
```