Add simplebook ansible roles

[slifty]

This PR creates two categories of Ansible script for SimpleBook:

• Scripts to install the SimpleBook services.
• A role to install the SimpleBook plugin into a competition.

This PR does not actually install the SimpleBook plugin in a given competition.

To install SimpleBook in a competition (e.g. locally for testing):

1. replace - collection with - simplebook in the competition .yml file (e.g. competitions/LLIIA2020/ansible/LLIIA2020.yml).
2. Add simplebook_git_version: main to the appropriate inv/{scope}/group_vars/all.tmpl

Resolves #110

[hawkinsw]

I don't know enough about Ansible to give a meaningful review. However, I see nothing that is an immediate cause for concern!

[frankduncan]

I think some of the changes are probably worth discussing, so marked as request changes. The only other thing to request is that an ansible group for "demo" to be created, which starts up on a different port (see torquedata). Then allow the port to be configurable in the inherited simplebook mediawiki extension role. That way, we can set the DemoView competition to use the demo version of simplebook running on the production box.

[frankduncan]

I have gone back and forth on whether we should tag the git_versions to a moving target. But at least for production, and likely demo (in the prod/group_vars/all), we should set to a version. That way we know, for a given deployment of a version of torque-sites, it corresponds directly to a sha, so re-running the ansible-playbook without updating torque-sites installs the same system, and no one accidentally breaks production by accidentally checking in breaking code to simplebook/main

[slifty]

I agree with the hard-lock of a version BUT would like to wait to do that until after we have a SimpleBook@1.0.0 -- right now locking in a version would be locking in a broken version since it isn't working yet.

Mind if we keep it main for now and when we come back and actually deploy it for a competition, update this to point to the v1 tag?

[frankduncan]

Totally fine. Though we (really, I) have been using shas instead of tags as that provides more flexibility. That's not an endorsement, though :)

[frankduncan]

Changes talked through, good to go :)