muster release v5.42.1

Fixed

• An expired token’s error reads token has expired for <server>, re-authenticate to refresh. A forwarded or exchanged token that was merely past its expiry ended its error in %!w(<nil>), and the connect log printed <nil> as its cause. The message now ends at re-authenticate to refresh; a token with no parseable expiry says it is unusable and carries the parse error. (#1511)