muster release v5.39.2

Fixed

• muster auth token renews an access token in its last minute instead of answering auth_required. The CLI’s token store calls a token invalid 60 s before it expires, while the transport renewed only a token past its expiry: a command in that minute connected with the old token unrenewed, then found no valid token and answered auth_required: authentication required … sign in with muster auth login, although the refresh token was good and a call a minute later went through. A client that runs muster auth token per call (a script, a watch reading through call_tool) read that as a lost sign-in. The transport now sees the expiry the store judges by, so a connection in the last minute renews the token first. Without a refresh token, or with one the authorization server refuses, the command still answers auth_required. (#1450)