From the ETL pipeline work on June 22, 2021

There are places where we want to specify what the name in the output
is, rather than letting it inherit.  At the same time, changed
LinkedSecondSheet to take a list of dictionaries, rather than multiple
arguments.

This required, for some of the competitions, to run the data through
dos2unix, which changed the shas.  But also, at the etl library level,
we needed to remove the unicode <feff> character that sometimes gets
added to the start of the csvs.

It didn't get changes after the ansible refactor, and so failed to work
with the mediawiki upgrade correctly.  This brings it up to date with
the rest of the competitions, and corrects some other errors (like
referencing proposals instead of LFC100Change2020 in etl pipeline) so
that it once again works in production.

This competition was deemed no longer required, as it was a vestige of a
time long past.  It was removed from production, and thus also from
here.

There's also a correction of a miscommit on the start of this that left
the script in a bad place.

This required forcing all the competitions with Annual Operating Budget
to match values with each other, so that the global TOC worked.  To that
end, code was put into the central etl library.

Also adds the export tables role to all the competitions.

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.

This updates all competitions to use simplebook instead of collection.

If an existing deployment is using collection, the wiki configuration
must be manually updated (or explicitly replaced) so that both
simplebook and collection are not present at the same time

Issue #122

ECW2020 can now ingest finalist attachments with a CSV mapping between
the zip folders and the proposal IDs.

Issue #126

ECW2020 loaded the new deploy tooling but didn't invoke it for
decryption. This is no longer the case!

This is the first competition to use SimpleBook, so adding it
individually even though we will not want to do this on
a one-commit-per-competition basis down the line.

This sets up LLIIA2020 to use the simplebook role instead of the
collection role.

Issue #122

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