This only happens in some places, not on page loads.  But it breaks
javascript in weird ways as browser tries to render extra thigns.  This
manifested as breaking visual editor.

Change is based on https://www.mediawiki.org/wiki/Manual:$wgUser

Because we now have a deployed wiki that is not torque enabled (the help
wiki), and that wiki also needs simplebook installed, we need to split
the configuration between the base that installs simplebook, and the one
that manages the connection to torque.

Now that simplebook is in production, the old system can be completely
removed.  It's also been removed from production.

There are some wikis that don't need a csv2wiki or mwlib user.  For
those, we shouldn't attempt (and fail) to create the users.

* Removes nodejs coming from apt
* Sets the simplebook git version to a sha (so that re-deployments are
  consistent in production)

Instead of removing the link via editing the sidebar, just hides it via
css.  The sidebar edit proved too much of a hassle, in that it didn't
actually work correctly.

Issue #131: Remove 'Printable version' tool from all Torque wikis

This change was made in the SimpleBook plugin, so it no longer required.

Also adds the export tables role to all the competitions.

Vector in mediawiki 1.35.0 made it so that portlets like the one in
torque on the left menu are hidden, so this overrides that.

Lots of little changes to pave the way for it.  New variables need to be
set, and version numbers need to be updated.

This is for a mediawiki extensions that allows downloading tables as
csvs/xlsxs.

100Change2017 and 100Change2017Partners use postgres, while everything
else can use mysql.

Pages were cutting very close to the bottom when printed; this adds
a 50px margin on all sides of the page.

Issue #120

There was an issue with long URLs breaking word wrap and the solution at
the time was to set a very wide min-width. This is not ideal for all
viewports, including printing, so we are moving to a word-wrap rule.

Because of flex box there is an additional improvement necessary, which
is that flex-boxes will specify a default min width of whatever the
longest element (before word breaks).  By specifying a smaller min-width
we prevent that auto calculation.

https://stackoverflow.com/questions/36150458/flex-item-overflows-container-due-to-long-word-even-after-using-word-wrap/36150638

Issue #120

The torque view was being improperly parsed as being the literal string
`"false"` in situations where no view had been set.

Issue #118

Now that globalview is fully deployed in production, it can be the prod
ansible target, holding port 5000, and the sha for that TDC extension
can be set to the globalview aware one.

This adds a new `simplebook` role that compettion scripts can invoke.

A competition can use this ansible role to install the SimpleBook
mediawiki plugin to a given instance. It's similar to the existing
`Collection` role.

Issue #10

This includes:
* Reverting changes to LoneStar as it's not the first competition going
* Changing LLIIA2020 from GV, since this is going live
* Parameterizing the torquedataconnect role's git checkout so old
  competitions are broken by this
* Other small whitespace fixes

This required a few small changes to LoneStar and LLIIA, in that the
competitions needed to be renamed to GVLoneStar and GVLLIIA, so that
they could exist on the production server alongside their non Global
View enabled counterparts.

Otherwise, this large change builds out the initial deployment of Global
View, including:
* The GV ansible config
* The GV pipeline
* The GV enablign etl changes to LLIIA and LoneStar
* The base etl changes to add common Global View data
* Update to torquedata for the new deployment of the django enabled
  torquedata

There was a potential bug where simplesaml autoconfig would populate
with an empty '' => '' if the okta variables were not set.

This adds a conditional, skipping that step if there is no value
present.  There are still potentials for error in the event that
simplesaml is never provided any value, however, as at least one
authentication endpoint must be defined for simplesaml to work.

Issue #93

Mediawiki sometimes needs the php-mysql task to run.  It doesn't really
hurt to proactively include it here (we already do so for psql).

The alternative would be to remove database dependency installations
from the mediawiki task and require that the calling role determine
which dependency to include, but that is a larger scope concept and not
necessarily something we would prefer anyway.

Issue #93

Ansible will, by default, overwrite permissions for a mysql user when
setting new permissions.  This modifies the task so that it enables
`append` mode. That way if you are re-using names you won't find
yourself unhappily and unexpectedly lacking permissions.

Issue #85

See code adjacent comment in diff for more information.

This, in addition to the other configurations in the .htaccess file, is
needed so that large result sets from the API will not error out.

(See https://chat.opentechstrategies.com/#narrow/stream/\
45-Lever-for.20Change/topic/API/near/97885 for context.)

Because individual competitions may want to add their own tabs, the lfc
anaylysis needs to be dynamic on an array, rather than explicitly adding
tabs.  This was mainly needed for 100Change2020, but will probably be
necessary for future competitions as individual pdfs get their own tabs

Mainly the addition of LFC Admins and LFC Pseudo Decision Makers.

Before the ansible refactor, we were copying and pasting a lot of
ansible configs.  Instead of copying and pasting the large tar balls
that went with those deployments, they all lived in a central
'thirdparty' directory.  However, that creates confusing ansible
playbooks and directory structure, and it's much simpler to have things
co-located.  This resolves that change.

This is needed by api users, who are pulling down large sets of data, as
the torque api puts it all in memory before rendering it for the
download.

A part of the ansible refactor, the permissions for users needs to be
more fleshed out.  This adds specific groups for the api partners.

This involved updating a whole bunch of config, and more so in the opass
world (for OTS users), as well as removing the duplicate simplesaml
deployment host.

1) enable for sysops, and 2) hide the mediawiki [Edit] section links
when the proposal has edit enabled.

Based on conversations with MacFound, the base way we want to log into
competitions should be okta, with a locallogin.php option for special
cases.  That means that before, where competitions that defaulted to
okta were the exception, and had the overriding configuration in their
ansible tasks now need to do nothing.  Competitions that need to always
have the local login option (due to legacy reasons) enabled are now the
exception, and have those exceptions in their ansible files.