Fix: crmd: hard error if remote start fails due to missing key

Previously, if the remote authentication key were missing or unreadable on the
connection host, the connection would be repeatedly re-attempted (and failed)
until the start timeout, then recovery would start the process over.

Now, an unavailable key is treated as a hard error, banning the node from
hosting the remote connection.