muster release v5.32.8

A rolling muster takes traffic only once it can mint tokens. The chart’s readiness probe read /health, which answers 200 while OIDC discovery is still pending, so a new pod joined the Service and the old one was stopped while the new one still answered every /oauth/token with 503 service_unavailable (“OIDC discovery in progress”) – a burst of failed exchanges for every client at once, the Developer Portal’s cluster-token exchange across all installations included. The new /readyz answers 503 until discovery succeeds and the chart’s readiness probe uses it; /health stays the liveness probe and keeps answering 200, so a Dex outage still does not restart the pod. (giantswarm/giantswarm#37348)