fix: postgress-operator validation (#67)

## Description
The validation for the postgres-operator component was checking for
resources in `postgres` rather than `postgres-operator`
...

## Related Issue

Fixes #N/A

## Type of change

- [ x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)

## Checklist before merging

- [x ] Test, docs, adr added or updated as needed
- [x] [Contributor Guide
Steps](https://github.com/defenseunicorns/uds-package-postgres-operator/blob/main/CONTRIBUTING.md#developer-workflow)
followed

---------

Signed-off-by: Chris Harden <[email protected]>
Co-authored-by: Wayne Starr <[email protected]>
Release-As: v1.13.0-uds.3

common/zarf.yaml

@@ -34,9 +34,15 @@ components:
             wait:
               cluster:
                 kind: packages.uds.dev
-                name: postgres
-                namespace: postgres
+                name: postgres-operator
+                namespace: postgres-operator
                 condition: "'{.status.phase}'=Ready"
+          - description: Validate Postgres Package
+            maxTotalSeconds: 300
+            cmd: |
+              if ./zarf tools kubectl get packages.uds.dev postgres -n postgres; then
+                 ./zarf tools wait-for packages.uds.dev postgres -n postgres '{.status.phase}'=Ready
+              fi
           - description: Postgres Operator to be Healthy
             maxTotalSeconds: 90
             wait: