muster release v5.34.8

muster waits for its Valkey at start instead of crash-looping. When muster and its Valkey restarted together (a reclaimed node), muster gave up on the session-store Valkey after 20 s and exited with mcp-aggregator service failed; the kubelet restarted it until Valkey was up (five restarts in three minutes, a ContainerRestartingTooOften page, every MCP call a 503). Now muster keeps dialling with capped backoff (1 s doubling to 8 s), one Valkey for the session stores did not answer, retrying line per attempt, and binds its port once Valkey answers: the pod is not ready while it waits and ready within seconds after. The chart’s new startupProbe (/health, every 5 s, 60 failures) keeps the liveness probe off for up to 5 minutes of start. Only a configuration error ends the start: credentials or database refused, a malformed address, a certificate that does not verify. (#1364)