forced masters should not respond to clients when they're not the master...

...,

as this could mean some updates are not yet applied to the store


This fixes a bug where when restarting the forced master it does not yet apply the latest value from it's tlog to the store before it starts responding to client requests. This too eager responding might return outdated data (and resulted in a failure on CI).

Ran it on CI, looks good, except for 1 bug, which I will not solve in this PR.
I have a fix for it already on the branch timeout-accepteds-check-done which should hopefully soon get a PR too (if it doesn't I'll apply the fix on a new separate branch).