Feature/78 4th and 5th endpoint work

[windoverwater]

At a high level this PR contains the following work:

• add support for the web-api interface to function (various odds and ends)
• split the original implementation of using the logging module for BOTH logging and printing (which was probably a bad thing but that is history) into logging and a wrapper around either printing to STDOUT or printing to data structure which can be directly returned to the web-api. This is to initially support passing the verify-ballot, tally-election, and show-contest text/log/json data back to the web-api. The idea is to just get it done for the demo and to refactor it later
  • the print wrapper was added to the Operation class for convenience. Again the thought is that this can be refactored after the demo
  • Ion and I talked about this but never did anything about it - I picked a random design and implemented it here now
• changed ElectionConfig from being a single global value (which does not support the web-api model) to a cache with one level. This will allow the CLI demo to still run as is (the cache should be hot for the entire CLI demo) while also allowing the web-api demo to run (across multiple different git workspaces in parallel). But this needs to be reviewed carefully as I may not be understanding how FastAPI is handling async endpoints.
• removed the super().init calls from the ops package constructors as they become redundant

Creating this PR early so there is time to potentially address issues in case it wants to be included in the release branch.

[windoverwater]

@ion-oset @stratofax I know you guys are busy, but I would like to have plenty of time to address any comments to this PR before the code freeze. And this PR has been open for a while. Said another way, if there are no comments today, let me know if it is NOT ok to merge this as is with a comment here. I would to merge it by tomorrow.

[ion-oset]

All your fixes LGTM.