Runner stuck in message loop when token invalid

[maskati]

Describe the bug
Runners can get stuck in a message acquisition loop from which they never recover:

√ Connected to GitHub
Current runner version: '2.310.2'
Listening for Jobs
Runner connect error: The signature is not valid.. Retrying until reconnected.

The error is most likely thrown in the GetNextMessageAsync loop, as a result of a SignatureValidationException.

To Reproduce
Typically occurs when concurrent runner registrations initiated for the same runner name, where one replaces the other. This seems to invalidate the token in GH, resulting in token validation errors.

Expected behavior
Runners should bail on non-transient error conditions, such as invalid tokens.

Runner Version and Platform

Linux 2.310.2.