remake: no --follow-strict-remakes; a strict remake failing says who

A strict remake takes a majority of members whose --strict-keys take
its manifest's signer: no node votes for one without, so
--follow-strict-remakes (1173) goes. A node that doesn't vote still
switches once the others commit, as with any remake.

So that an operator can tell why one fails: a strict remake aborted
for want of a majority (the voting period over, or a majority out of
reach) says in its reason (GET /admin/remakes/{id}, and the
coordinator's log) which members didn't vote, and that a member votes
for one only with its manifest signed by a key of its --strict-keys.
Each of those logs why itself (`Not voting for a strict remake`).

The sim a_strict_remake_too_few_take: only a takes the manifest; the
remake aborts, naming b and c.

1 files changed, 0 insertions, 4 deletions

diff --git a/src/state/host.rs b/src/state/host.rs
index 82b6c7c..ac36171 100644
--- a/src/state/host.rs
+++ b/src/state/host.rs
@@ -424,10 +424,6 @@ impl Host for AppState {
         &self.strict_keys
     }
 
-    fn follows_strict_remakes(&self) -> bool {
-        self.follow_strict_remakes
-    }
-
     fn begin_rejoin(
         &self,
         target: Epoch,