fix(consul-postgres-ha): deregister legacy Pattern B proxy IDs at sidecar startup

Survives an in-place upgrade from the previous Pattern B shape
(`Kind: connect-proxy` with ID `${parent}-sidecar-${peer}`).
`/consul/data` is a persistent volume, so the stale registration
survives container restarts; if it lingers alongside the new
inline-`SidecarService` shape, `consul connect envoy -sidecar-for`
sees two matches and refuses to render. Deregister the known legacy
IDs idempotently before each PUT.

Safe to remove this block in a future release once no live cluster
predates the inline-SidecarService landing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: h4x3rotab

consul-postgres-ha/mesh-sidecar/entrypoint.sh

@@ -279,6 +279,18 @@ if [ "$ROLE" = "worker" ]; then
       TAGS_JSON='[]'
     fi
 
+    # Defensive cleanup: a prior boot may have used different IDs for
+    # the same logical proxy (e.g. an earlier release of this image
+    # registered Pattern B as `Kind: connect-proxy` with ID
+    # `${parent}-sidecar-${peer}`). Consul-data is a persistent volume
+    # so the stale entries survive container restarts; if they linger
+    # alongside the new inline SidecarService, `consul connect envoy
+    # -sidecar-for` sees two matches and refuses to render. Deregister
+    # known stale IDs idempotently before we PUT the new spec.
+    for stale_id in "${PARENT}-sidecar-${PEER_ID}"; do
+      curl -fsS -X PUT "http://127.0.0.1:8500/v1/agent/service/deregister/${stale_id}" \
+        >/dev/null 2>&1 || true
+    done
     jq -n \
       --arg name "$PARENT" \
       --arg id "$PARENT_ID" \