Wait for dashwise and tududi in CI, document both

The deploy job only waited on the deployments that existed when it was
written, so a broken rollout of either new app would have been reported
as a successful deploy.

Also records the two new secrets in the bootstrap table, and the two
traps found while adding these: dashwise publishes :latest for amd64
only, and a server-side dry run of a brand new namespace reports every
resource inside it as missing until the namespace exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.gitea/workflows/deploy.yaml

@@ -93,13 +93,13 @@ jobs:
           kubectl rollout status deploy/pihole -n pihole --timeout=10m
           kubectl rollout status deploy/unbound -n pihole --timeout=10m
           kubectl rollout status deploy/unifiedstreaming -n unified-streaming --timeout=10m
-
+  
       - name: Deployment summary
         if: always()
         run: |
           echo "## Deployment Summary" >> $GITHUB_STEP_SUMMARY
           echo '```' >> $GITHUB_STEP_SUMMARY
-          for ns in bitwarden default home-assistant nginx pihole unified-streaming; do
+          for ns in bitwarden default dashwise home-assistant nginx pihole tududi unified-streaming; do
             kubectl get deployments -n $ns >> $GITHUB_STEP_SUMMARY || true
           done
           echo '```' >> $GITHUB_STEP_SUMMARY