Validate Postgres Package fails when postgresql is disabled

[JeffResc]

Steps to reproduce

1. Deploy with postgresql.enabled: false

Expected result

Deployment succeeds with no warnings or errors

Actual Result

2025-07-30 18:52:48 INF running command cmd=Validate Postgres Package
2025-07-30 18:52:48 INF waiting for action cmd=Validate Postgres Package timeout=300
2025-07-30 18:52:48 DBG running command shell=sh cmd=if /usr/local/bin/uds zarf tools kubectl get packages.uds.dev postgres -n postgres; then
   /usr/local/bin/uds zarf tools wait-for packages.uds.dev postgres -n postgres '{.status.phase}'=Ready
fi
2025-07-30 18:52:50 DBG action complete cmd=if /usr/local/bin/uds zarf tools kubectl get packages.uds.dev postgres -n postgres; then
   /usr/local/bin/uds zarf tools wait-for packages.uds.dev postgres -n postgres '{.status.phase}'=Ready
fi
 stdout= stderr=
 NOTE  Using config file bundles/core/uds-config.yaml
Error from server (NotFound): packages.uds.dev "postgres" not found
2025-07-30 18:52:50 INF action succeeded cmd=Validate Postgres Package stdout= stderr=

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Low, just a warning but deployment succeeds

Additional Context

The Validate Postgres package here should be conditional based on the postgresql.enabled value just like the package itself is.

[zachariahmiller]

good callout. We cant properly make that optional via the value, but we can check if the namespace exists or something similar and if not skip the check