Break election components apart

[brandonfancher]

This componentizes and organizes the election UI. After this PR, we can refactor this to depend on subchain queries. And I'm sure we'll find more opportunities for refactoring as we do that.

[brandonfancher]

I'd like for this to always pull the current datetime so that the election is active after this runs...but haven't figured that out yet. That can be done in a subsequent PR.

[sparkplug0025]

praise: nice touch!

[sparkplug0025]

suggestion: we can centralize the elections scenario in the current run-full-election.wasm file and use checkpoints to stop the runner where we want. For instance, as opposed of creating this file, just add this start_election to the bottom of the full-election one with a checkpoint:

   r.tester.genesis();
   r.tester.run_election(true, 10000, true);
   r.checkpoint("small_election");
   r.tester.induct_n(100);
   r.checkpoint("inductions");
   r.tester.eden_gm.act<actions::electsettime>(s2t("2021-11-16T18:45:00.000"));
   r.checkpoint("full_election1");
   r.tester.start_election(true, 10000);

If someone wants to avoid the start of the new election they can just do cltester run-full-elections.wasm -c full_election1

I also think since we are using checkpoints we should rename the file from run-full-elections to run-elections, then it's more generic about elections scenarios....

[brandonfancher]

Oh, cool! That’s awesome!

[sparkplug0025]

LGTM! With the checkpoint suggestion you can remove the new files and cmake changes :)