chore(woodpecker): drop the transitional commonAnnotations prune-guard (stage 3)

Final stage of the seed-woodpecker -> dedicated woodpecker KS move. The
commonAnnotations prune:disabled guard on apps/woodpecker/ has done its job: the
ownership handoff completed (verified — wp-pg + all app objects adopted by the
woodpecker KS, RESTARTS=0, nothing pruned), so the app objects no longer need
blanket prune protection and should be normally prunable by their owning KS again.

Removes only the commonAnnotations block. The 4 CNPG DB objects keep their
per-file prune: disabled (permanent data-guard on Cluster/wp-pg etc.) — verified
kubectl kustomize apps/woodpecker now annotates exactly those 4, not the 13 app
objects.

Rolls woodpecker-server + agent once more as the annotation leaves their pod
templates — the same accepted CI restart as stage 1.

Co-Authored-By: Claude Bot <claude-bot@renner.uno>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

kubernetes/apps/woodpecker/kustomization.yaml

@@ -1,16 +1,5 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
-# TRANSITIONAL prune-guard for the seed-woodpecker -> dedicated woodpecker KS
-# split. These app objects (incl. the woodpecker-ci Namespace and the live
-# server/agent) currently belong to the catch-all `apps` KS; when `woodpecker/`
-# is removed from apps/kustomization.yaml and the dedicated `woodpecker` KS
-# takes over, this annotation stops the apps KS from pruning them mid-handoff.
-# NOTE: kustomize propagates commonAnnotations into the Deployments' pod
-# templates, so applying/removing this rolls woodpecker-server + agent once each
-# — accepted (CI restart is fine). Removed once the new KS owns them (final
-# stage) so the app objects are normally prunable again.
-commonAnnotations:
-  kustomize.toolkit.fluxcd.io/prune: disabled
 resources:
   - rbac.yaml
   - server.yaml